On Wed, 2011-01-26 at 18:10 +0100, Christophe Laprun wrote:
On Jan 26, 2011, at 6:03 PM, Julien Viet wrote:
> it was kind of possible in JPB, when you redeployed UI admin in JSF.
>
> it should work the same in GateIn (or if it does not we could).
I was talking about the fact that you could basically hot deploy the WSRP service as a
sar file in JBP and it would add the appropriate admin page / portlet and service. If you
didn't want WSRP, you could just remove the sar file and you were done, no other
dependency anywhere else. It didn't quite work completely hot but at least it was
possible to add/remove the service in an appropriate manner while the server was stopped
regardless of whether the service was present when the server was *first* started…
I looked into this a one point, and had deployment of portlets and page
somewhat working. It used the same pages.xml and navigation.xml as the
extension mechanism. It was basically what the extension mechanism was
doing except it didn't have the checks if it was the first time doing so
or not.
The problem I ran into and couldn't get around was an exo kernel
dependency issue, when the server would shut down, the DataStorage
remove methods would not persist the change. Whatever was persisting the
changes was being shutdown too quickly (the same remove methods did work
if called before the server shuts down).
[I also had hot deploy kindof working as well, but it was the opposite
as above. It would only work when the server was already started, not
during startup or shutdown. The two options combined may have worked]
I'm not asking for hot (un-)deployment but I'd like to at
least be able to package my service in one *single* file that could be added/removed
cleanly anytime the server is stopped…
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn:
http://blog.gatein.org /
http://twitter.com/gatein
Follow me:
http://metacosm.codepuccino.com /
http://twitter.com/metacosm