Hi Chris,
This behavior is totally normal, we want to have dedicated services for each portal container. The goal behind this, is to allow the customer/partner to decide which portlets must be deployed on each portal (i.e. portal container). Up to now, it is not possible since the PortletApplicationDeployer is not aware of portal containers but it will be the next step (the first step was to register the PortletContainer at the portal container level instead of the root container). FYI, it is already possible to decide which google gadgets, javascript files, skins and configuration files must be deployed on each portal.
I hope it helps,
BR,
Nicolas
Hi,
I haven't followed the ins and outs of the new packaging but there's
definitely something wrong with it. It shouldn't initiate services
several times. As of now, the WSRP service (and probably the other
services as well) is started twice, once each for sample-portal and
portal PortalContainers. I'm not quite sure what the intent is but to
me, portals should reuse services, not start new instances.
Can anyone please clarify what the situation is?
Thanks in advance.
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow JBoss Portal: http://jbossportal.blogspot.com / http://twitter.com/jbossportal
Follow me: http://metacosm.codepuccino.com / http://twitter.com/metacosm
_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev