[gatein-dev] Packaging question

[Nicolas Filotto]

No If you really want to instantiate it only once as a singleton you need to
tie it to the RootContainer instead of a PortalContainer which is currently
the case as the component "ExoKernelIntegration" has been declared into the
file portal.war/WEB-INF/conf/common/portlet-container-configuration.xml
which is used to instantiate a PortalContainer. If you want to tie it to the
RootContainer, you need to defined this component into the file
conf/configuration.xml of the project exo.portal.component.pc. Please refer
to this wiki article to better understand how the ExoContainers are
initialized
http://wiki.exoplatform.com/xwiki/bin/view/Kernel/Container+Configuration

On Thu, Oct 22, 2009 at 1:45 PM, Christophe Laprun <claprun at redhat.com>wrote:

>
> On Oct 22, 2009, at 9:47 AM, Patrice Lamarque wrote:
>
> > Hello Chris,
> >
> >
> > The "GateIn Portal Sample Portal" is a demonstration on how we can
> > deploy a 2nd portal container on top of GateIn.
> > It means that your GateIn instance can now hos 2 fully independent
> > portal with their associated services.
> >
> > Put it simply it means you can run :
> >
> > http://localhost:8080/portal
> > http://localhost:8080/sample-portal
> >
> > The 2 URLs point to completely independent portal instances
> > (including services and JCR). The only thing they share is the
> > RootContainer.
> >
> > I guess WSRP is deployed in the portal container (/conf/portal/
> > configuration.xml), so it is perfectly normal that it be deployed
> > twice. First time in "portal" container, second in "sample-portal"
> > container.
> >
> >
> > To share services, there is the notion of virtual portal ex: (
> http://localhost:8080/portal/classic
> > , http://localhost:8080/portal/classic2 ) but that's something
> > completely different.
>
>
> Except that the WSRP service is not conceived to be instantiated twice
> at this time, it's conceived as a singleton. The current setup is
> currently causing issues because for example, despite the supposed
> separations, both portals still rely on the WSRP service publishing
> its WSDL under the wsrp-producer context. Also, going through the
> instantiation twice is also causing issues. I'd rather not deal with
> this complication at this point as there is already much work to do
> with WSRP and a single portal. You're welcome to take a look at how
> WSRP could be packaged so that it can be instantiated several times
> without causing issues, I just don't have time to work on that now.
>
> As an added remark, I just need to get rid of gatein-sample-portal.ear
> to remove the sample-portal instance, right?
>
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
>



-- 
Nicolas Filotto
JCR Product Manager
Project Manager
eXo Platform SAS
nicolas.filotto at exoplatform.com
+33 (0)6 31 32 92 19
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/gatein-dev/attachments/20091022/c5711511/attachment-0001.html