xmlaccess 部署带有库参考的 portlet
我在使用 xmlaccess 部署 JSR168 portlet 时遇到问题。我在部署和加入具体页面方面没有问题，但我想自动添加共享库引用。是否可以？？我使用 IBM WS 控制台添加了名为“libshared”的共享库。我可以使用 xmlaccess 在输入 xml 中添加此引用吗？
I have problem with deploying JSR168 portlet using xmlaccess. I have no problem with deploy and join to conrete page but I would like to add shared library reference automatically. Is it possible?? I added shared library named 'libshared' using IBM WS console. Can I add this reference in input xml using by xmlaccess?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我认为您不能在 xmlaccess 中执行此操作。但是您可以尝试将对库的引用放在 portlet 的 war 文件的 META-INF 目录的 Manifest.MF 文件下。
或者可以将共享 jar 文件放在 /shared/ext 目录下。或者您可以将其放入 wps.ear 文件中。请注意，这两个解决方案中的任何一个都将与整个门户安装共享您的库，而不仅仅是选择 portlet。
I don't think you can do this in xmlaccess. But you may try putting a reference to the library under the Manifest.MF file of the META-INF directory of your portlet's war file.
Or could just put the shared jar file under your /shared/ext directory. Or you could put it inside your wps.ear file. Mind you, either of these two solutions would share your library with the entire portal installation, rather than just select portlets.
您可以使用 wsadmin 或类似工具部署应用程序，并使用它来更新类路径（即共享库），然后您可以使用 xmlaccess 来部署 portlet 并引用先前部署的应用程序 - 尽管我认为这可能只在 WebSphere Portal 中有效6.1.
如果您需要更多详细信息，请给我打电话。
You can deploy the application using wsadmin or similar and use that to update the classpath (i.e. for the shared library), you can then use xmlaccess to deploy the portlets and reference the previously deployed application - although I think this may only work in WebSphere Portal 6.1.
Give me a shout if you need further details.
不久前我也遇到了这个问题......并对其进行了最大程度的研究，包括花一些时间与 IBM 的各个级别的支持人员交谈。
XMLAccess协议不提供这种与 Portlet 应用程序部署一起的“系统级”配置；它只能用于安装、定制和卸载 Portlet 应用程序及相关工件。如果您的部署策略涉及直接通过
XMLAccess部署 WAR 文件，那么您将必须通过 WAS 管理控制台手动将共享库添加到应用程序；这必须手动完成，因为当通过 XMLAccess 部署 WAR 文件时，WebSphere Portal 将创建一个具有随机名称的 EAR 来“托管”您的 WAR 文件；因此您无法编写共享库附件的脚本。（或者，您可能希望将共享库添加到服务器的 (
WebSphere_Portal) 类路径中）如果您的部署策略涉及部署打包为 EAR 的 Portlet 应用程序，那么您的处境会更好；您可以将共享库附件自动化作为 EAR 部署过程的一部分，然后使用 XMLAccess 向 WebSphere Portal 通知您的 Portlet 应用程序在 EAR 中的位置（这就是 Michael 上面提到的；它在 WebSphere Portal 6.0 中的工作方式为出色地）。
祝你好运。
I encountered this as well, a while ago... and researched it to the max, including spending some time chatting with IBM's support in various levels.
The
XMLAccessprotocol doesn't provide for such "system-level" configuration alongside Portlet application deployment; it can only be used to install, customize and uninstall Portlet applications and related artifacts.If your deployment strategy involves deploying WAR files directly through
XMLAccess, then you will have to manually add the shared-library to the application through the WAS admin console; this will have to be done manually because, when deploying WAR files through XMLAccess, an EAR with some random name is being created by WebSphere Portal to "host" your WAR file; hence you can't script the attachment of a shared library.(alternatively, you may wish to add the shared library to the server's (
WebSphere_Portal) classpath)If your deployment strategy, instead, involves deploying Portlet applications packaged as EARs, then you're in a better position; you could automate the shared-library attachment as part of your EAR deployment process, then use XMLAccess to inform WebSphere Portal about the location, in the EAR, of your Portlet applications (which is what Michael mentioned above; it works in WebSphere Portal 6.0 as well).
Good luck.