You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by David Jencks <dj...@apache.org> on 2005/02/01 01:32:51 UTC

Re: JS2 deployment

On Jan 31, 2005, at 1:27 PM, Marcel wrote:

> Randy,
>
> Thanx for pointing out the reason why most of the JBossManager's  
> methods have been stubbed out. Maybe it is a good idea to document  
> this in the source itself.
>
> I've just read Tom Pesendorfer's reply in a different thread, pointing  
> me at his wiki update.
> On the wiki he describes that the portlets need to be undeployed each  
> time JBoss is stopped and restarted, see  
> http://wiki.apache.org/portals/Jetspeed2/JBossHowToDetailed#head 
> -5632971a9f0137c586f3c1da93e50dc9bea7604b.
> I think this needs to be improved such that JBoss can be restarted  
> without interferring with jetspeed's portlets.
>
> I do not know the full details of the JBoss hot deployment  
> functionality, but for general web applications it suffices to drop  
> the war file in the deploy directory, it is then automatically  
> deployed.

My comments are based on jboss as of about 2 years ago.  JBoss 4 with  
jsr-88 deployment may possibly work differently and be more amenable to  
what you want.
What you want may be difficult to arrange.  JBoss undeploys everything  
on shutdown, and redeploys it automatically by scanning the hot-deploy  
directories on startup.  If you leave the portlets "deployed" on  
shutdown, what will happen when the portlet application gets redeployed  
on startup?  How will you determine if differences between the  
persisted state of the portlets is due to things like customization or  
due to changing the portlet application itself?

thanks
david jencks

>
> I am quite happy to cooperate with you on this.
>
> Marcel
>
> Randy Watler wrote:
>
>> Marcel,
>>
>> I am not familiar with deployment under JBoss. However, the  
>> implementation is stubbed out because the inderlying file system PAM  
>> deployment strategy might have been thought to be sufficient. Perhaps  
>> it is not.
>>
>> I am wondering what you intended to do while customizing/implementing  
>> the JBossManager. I was also looking for any insight you might have  
>> on the general approach of letting JBoss simply pick up webapps war  
>> files dynamically dropped into its deployment directory. In  
>> otherwords, how and does JBoss implement an autoDeploy or liveDeploy  
>> Tomcat equivalant?
>>
>> Anyway, if you do develop/implement JBossManager, I still plan on  
>> being able to support it since I am leaving the existing PAM  
>> implementation functional.
>>
>> Randy
>>
>> Marcel Dullaart wrote:
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org