Re: [gatein-dev] Packaging question
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