Portlet.xml Not Merged for JSR Portlets That are Part of Separate Shared Libraries
Last updated on FEBRUARY 20, 2018
Applies to:Oracle WebLogic Portal - Version 10.3.0 and later
Information in this document applies to any platform.
When two or more JSR 168 portlets that are each part of separate shared libraries are added and consumed via a portal, only the portlet.xml for the portlet from the first library is picked up. This results in the following error when trying to display the portlet from the other shared library:
Where 'xxx' is the web application name and yyy is the portlet name.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms