Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008ynCM project_key: JBEPP Different initialization order prevents hot-deployment of Spring Portlets, which need the Spring RootContext (servlet) to be initialized first - see GTNPC-76 for details.
Link: Added: This issue depends GTNPC-76
Link: Removed: This issue depends GTNPC-76
Link: Added: This issue is a dependency of GTNPC-76
The Spring portlet bridge expects ordering that it shouldn't rely on. We cannot fix the Spring Portlet Bridge but we will investigate one more time if a workaround can be introduced. Ideally Spring Portlet Bridge would be fixed by the developers though.
Labels: Added: EPP_5_2_1_Candidate
Labels: Removed: EPP_5_2_1_Candidate
Link: Added: This issue is a dependency of JBEPP-1505
Added option to specify the deployment of a webapp in wci with respect to the initialization of a servlet.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: == HELPDESK CASE THAT WILL REQUIRE CCFR == CAUSE: CONSEQUENCE: FIX: RESULT:
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,9 +1,9 @@ == HELPDESK CASE THAT WILL REQUIRE CCFR == -CAUSE: +CAUSE: The spring portlets require the initalization ordering to be specified between a portlet and a servlet. This is not specified in the portlet specification, and is an issue on the part of the spring portlets for having this requirement. -CONSEQUENCE: +CONSEQUENCE: Spring based portlets work when the server is first started, but fail on hot deploy due to the requirement on portlet and servlet ordering. -FIX: +FIX: The WCI component has been updated to allow for the manual registration of a web application using a servlet. By specifying the load-on-start values between this registration portlet and the spring portlet, we can affect when the initialisation of a portlet happens with regard to a servlet. Note that this only guarantees when WCI will register a portlet, not when the PC initialises the portlet. Since the PC needs the web application to be registered in WCI, we can only guarantee that a servlet can be started before a portlet is initialise, which is the case for the spring portlet. -RESULT:+RESULT: Spring based portlets can now be configured to be hot deployable. There are multiple steps which need to be manually configured. See https://community.jboss.org/wiki/AdvancedWCIRegistrationFeatures
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,9 +1 @@ -== HELPDESK CASE THAT WILL REQUIRE CCFR == +Spring-specific portlet and servlet initialization ordering requirements caused Spring-based portlets to work when the server was first started, but fail on hot deployment. The fix introduces updates to the WCI component that allow manual registration of web applications that use a servlet. By specifying the load-on-start values between the registration portlet and the spring portlet, the way a portlet is initialized in relation to a servlet can be controlled. The fix only affects the point when WCI registers a portlet, not when the portlet is initialized. There are multiple steps which need to be manually configured. See https://community.jboss.org/wiki/AdvancedWCIRegistrationFeatures for more information.- -CAUSE: The spring portlets require the initalization ordering to be specified between a portlet and a servlet. This is not specified in the portlet specification, and is an issue on the part of the spring portlets for having this requirement. - -CONSEQUENCE: Spring based portlets work when the server is first started, but fail on hot deploy due to the requirement on portlet and servlet ordering. - -FIX: The WCI component has been updated to allow for the manual registration of a web application using a servlet. By specifying the load-on-start values between this registration portlet and the spring portlet, we can affect when the initialisation of a portlet happens with regard to a servlet. Note that this only guarantees when WCI will register a portlet, not when the PC initialises the portlet. Since the PC needs the web application to be registered in WCI, we can only guarantee that a servlet can be started before a portlet is initialise, which is the case for the spring portlet. - -RESULT: Spring based portlets can now be configured to be hot deployable. There are multiple steps which need to be manually configured. See https://community.jboss.org/wiki/AdvancedWCIRegistrationFeatures
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Spring-specific portlet and servlet initialization ordering requirements caused Spring-based portlets to work when the server was first started, but fail on hot deployment. The fix introduces updates to the WCI component that allow manual registration of web applications that use a servlet. By specifying the load-on-start values between the registration portlet and the spring portlet, the way a portlet is initialized in relation to a servlet can be controlled. The fix only affects the point when WCI registers a portlet, not when the portlet is initialized. There are multiple steps which need to be manually configured. See https://community.jboss.org/wiki/AdvancedWCIRegistrationFeatures for more information.+Spring-specific portlet and servlet initialization ordering requirements caused Spring-based portlets to work when the server was first started, but fail on hot deployment. The fix introduces updates to the WCI component that allow manual registration of web applications that use a servlet. By specifying the load-on-start values between the registration portlet and the spring portlet, the way a portlet is initialized in relation to a servlet can be controlled. This fix only controls when the web application is registered in WCI with regards to another servlet, and not the servlet ordering with respect to portlets. There are multiple steps which need to be manually configured. Refer to the Bugzilla directly for more information and links to setup information.