Author: chris.laprun(a)jboss.com Date: 2011-02-08 09:36:34 -0500 (Tue, 08 Feb 2011) New Revision: 5860 Modified: portal/branches/wsrp-extraction/component/wsrp/src/main/java/org/gatein/portal/wsrp/WSRPServiceIntegration.java Log: - Minor correction in comment. Modified: portal/branches/wsrp-extraction/component/wsrp/src/main/java/org/gatein/portal/wsrp/WSRPServiceIntegration.java =================================================================== --- portal/branches/wsrp-extraction/component/wsrp/src/main/java/org/gatein/portal/wsrp/WSRPServiceIntegration.java 2011-02-08 01:06:06 UTC (rev 5859) +++ portal/branches/wsrp-extraction/component/wsrp/src/main/java/org/gatein/portal/wsrp/WSRPServiceIntegration.java 2011-02-08 14:36:34 UTC (rev 5860) @@ -102,7 +102,7 @@ public WSRPServiceIntegration(ExoContainerContext context, InitParams params, ConfigurationManager configurationManager, ExoKernelIntegration pc, NodeHierarchyCreator nhc) throws Exception { - // IMPORTANT: even though PC ExoKernelIntegration and NodeHierarchyCreator is not used anywhere in the code, it's still needed for pico + // IMPORTANT: even though NodeHierarchyCreator is not used anywhere in the code, it's still needed for pico // to properly make sure that this service is started after the PC one. Yes, Pico is crap. :/ // todo: we currently only allow the service to go through initialization if we are running in the default portal