Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006kBBVIA2&sfdc.override=1 Steps to Reproduce: And this is also how the error can be reproduced, using $EPP_HOME/portletbridge/examples/seamEAR.ear: 1. Explode seamEAR.ear 2. Change context-root to contain a slash '/': <module> <web> <web-uri>seamBookingPortlet.war</web-uri> <context-root>/portalBookingDemo/demo</context-root> </web> </module> 3. Deploy the application 4. Start the server 5. Import all applications 6. Add the seamBookingPortlet to a new page: 11:59:46,926 ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet /portalBookingDemo.demo 11:59:46,926 ERROR [STDERR] at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:99) (If instead of importing all applications you try to add just the SeamBookingPortlet to a category, this already fails with a java.lang.NullPointerException.) Workaround: Workaround Exists Workaround Description: Current workaround: Change context-root to not contain slashes project_key: JBEPP I've tried to use a context-root with a slash "/" in a JSR-286 Hello World Portlet and it throws the following exception when trying to add it to a new page: 11:59:46,926 ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet /portalBookingDemo.demo 11:59:46,926 ERROR [STDERR] at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:99) Changing context-root to not contain slashes has fixed the problem. Problem happens when using slashes "/" in: - application.xml of an .ear file <module> <web> <web-uri>seamBookingPortlet.war</web-uri> <context-root>/portalBookingDemo/demo</context-root> </web> </module> Changing it to <context-root>/portalBookingDemo-demo</context-root> fixes the problem - jboss-web.xml of a .war file <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <context-root>/MySamplePortlet/SamplePortlet</context-root> </jboss-web> Changing it to <context-root>/MySamplePortlet.SamplePortlet</context-root> fixes the problem.
Link: Added: This issue is related to GTNPORTAL-434
Link: Added: This issue is related to GTNPORTAL-1834
Link: Removed: This issue is related to GTNPORTAL-434
Help Desk Ticket Reference: Added: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006kBBVIA2&sfdc.override=1
Steps to Reproduce: Removed: And this is also how the error can be reproduced, using $EPP_HOME/portletbridge/examples/seamEAR.ear: 1. Explode seamEAR.ear 2. Change context-root to contain a slash '/': <module> <web> <web-uri>seamBookingPortlet.war</web-uri> <context-root>/oag/ade</context-root> </web> </module> 3. Deploy the application 4. Start the server 5. Import all applications 6. Add the seamBookingPortlet to a new page: 11:59:46,926 ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet /oag.ade 11:59:46,926 ERROR [STDERR] at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:99) (If instead of importing all applications you try to add just the SeamBookingPortlet to a category, this already fails with a java.lang.NullPointerException.) Added: And this is also how the error can be reproduced, using $EPP_HOME/portletbridge/examples/seamEAR.ear: 1. Explode seamEAR.ear 2. Change context-root to contain a slash '/': <module> <web> <web-uri>seamBookingPortlet.war</web-uri> <context-root>/portalBookingDemo/demo</context-root> </web> </module> 3. Deploy the application 4. Start the server 5. Import all applications 6. Add the seamBookingPortlet to a new page: 11:59:46,926 ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet /portalBookingDemo.demo 11:59:46,926 ERROR [STDERR] at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:99) (If instead of importing all applications you try to add just the SeamBookingPortlet to a category, this already fails with a java.lang.NullPointerException.)
Needs new PC version which is bets now so postponed. Backporting is possible.
Upgrading PC is not necessary for this fix.
Release Notes Text: Added: When slashes were used in context path of portlet, it caused error.
Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Removed: When slashes were used in context path of portlet, it caused error. Added: In previous versions of JBoss Enterprise Portal Platform, an error would be encountered when slashes were used in the context path of a portlet. This issue has been corrected in this release.
Security: Removed: RHT+eXo Added: Public