[ https://issues.jboss.org/browse/GTNPORTAL-2700?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-2700: ------------------------------------ Description: When I deploy both Sample Extension and Sample Portal, only bundles from the sample portal EAR are used. Both sample portal and extension home portlet are showing "This is the Home Page of the "sample-portal"". (was: When I deploy both Sample Extension and Sample Portal, those bundles are used on both /portal and /sample-portal which are accessed first: when I visit /sample-portal first, both sample portal and extension home portlet are showing "This is the Home Page of the "sample-portal"" and vice versa, when I visit /portal first, both are showing "Congratulation, you just installed a new portal extension".) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2700?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-2700: ------------------------------------ Steps to Reproduce: (1) Make sure there is no older version of sample portal or sample extension in $JBOSS_HOME/gatein/extension. (2) Build Sample Extension and Sample Portal {code} cd /tmp git clone https://github.com/gatein/gatein-portal-quickstart.git cd gatein-portal-quickstart/gatein-portal-extension mvn clean package cp -t $JBOSS_HOME/gatein/extension ear/target/gatein-portal-extension.ear cd ../gatein-sample-portal mvn clean package cp -t $JBOSS_HOME/gatein/extension ear/target/gatein-sample-portal.ear {code} (3) Restart JBoss (4) * Visit http://127.0.0.1:8080/sample-portal ** OK: Home Portlet is showing: "This is the Home Page of the "sample-portal"" * Visit http://127.0.0.1:8080/portal ** NOT OK: Home Portlet is showing: "This is the Home Page of the "sample-portal"" ** EXPECTED: "Congratulation, you just installed a new portal extension" EDIT: The statement made in (4) can be made more precise as follows: Both /sample-portal and /portal show the same text for the given run of GateIn. However, the text differs between the individual runs of GateIn. Sometimes it is (a) ""This is the Home Page of the "sample-portal""" and sometimes it is (b) "Congratulation, you just installed a new portal extension". (a) is more frequent. Occurence of (a) vs. (b) seems to be random. Esp. it does not depend on the order of the first invocation of /sample-portal and /portal as I conjectured originally. was: (1) Make sure there is no older version of sample portal or sample extension in $JBOSS_HOME/gatein/extension. (2) Build Sample Extension and Sample Portal {code} cd /tmp git clone https://github.com/gatein/gatein-portal-quickstart.git cd gatein-portal-quickstart/gatein-portal-extension mvn clean package cp -t $JBOSS_HOME/gatein/extension ear/target/gatein-portal-extension.ear cd ../gatein-sample-portal mvn clean package cp -t $JBOSS_HOME/gatein/extension ear/target/gatein-sample-portal.ear {code} (3) Restart JBoss (4) * Visit http://127.0.0.1:8080/sample-portal ** OK: Home Portlet is showing: "This is the Home Page of the "sample-portal"" * Visit http://127.0.0.1:8080/portal ** NOT OK: Home Portlet is showing: "This is the Home Page of the "sample-portal"" ** EXPECTED: "Congratulation, you just installed a new portal extension" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2700?page=com.atlassian.jira.pl... ] Peter Palaga commented on GTNPORTAL-2700: ----------------------------------------- In ExoKernelIntegration there is {code:java} final ExoContainer topContainer = ExoContainerContext.getTopContainer(); FederatingPortletInvoker federatingPortletInvoker = (FederatingPortletInvoker)topContainer.getComponentInstanceOfType(FederatingPortletInvoker.class); if (federatingPortletInvoker == null) { federatingPortletInvoker = new FederatingPortletInvokerService(); topContainer.registerComponentInstance(FederatingPortletInvoker.class, federatingPortletInvoker); } {code} which probably causes that the same federatingPortletInvoker instance (plus the same linked invokers) is included in the invoker chain for every portal container. GTNPORTAL-2406 is related. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2700?page=com.atlassian.jira.pl... ] Peter Palaga commented on GTNPORTAL-2700: ----------------------------------------- The linked pull request is a dirty workaround, not a solution. A real fix should somehow achieve that federatingPortletInvoker in ExoKernelIntegration retains a reference to every instantiated producerPortletInvoker (and thus also transitive references to all its successor Invokers) not only the one instantiated in the first invocation of ExoKernelIntegration.start() method. In other words federatingPortletInvoker should be able to keep one local Invoker per portal and not only one for all portals as it is now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira