Re: JS2 deployment

[Randy Watler]

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:
Hi Randy,
Thanx for your answer.
I only want to make J2 run on JBoss 4.0.1.
At this moment I got J2 showing only title bars for the portlets but
lacking any content.
Since the JBossManager takes care of deploying the portlets under
JBoss, and it is not fully implemented, it only contains stub impl's
AFAIK.
That's why I thought I needed to implement it.
Marcel
On Mon, 31 Jan 2005 10:36:25 -0700 (MST), [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
 

Marcel,
I am working on this for the team. Can you post the details of what you
would like to accomplish in your custom ApplicationServerManager? The hope
is that we no longer need these custom implementations that are difficult
for us to support. The general approach is to rely on the auto/live
deployment features of the container instead of trying to interface to
each.
Details would be much appreciated at this point since I am reworking the
PAM implementation. I am also trying to keep the old deployer functional,
so if I succeed, you can always go back an use your ASM implementation if
necessary... hopefully not.
Randy
   

Hi David,
     

This means that we will no longer need specific code for application
       

deployment to each app server. In theory, this may solve our race
condition issues.
   

Does this in anyway influence the ApplicationServerManager interface and
     

its implementations?
   

I noticed that the JBossManager is not implemented, only stubs are
     

provided, and planned on implementing it.
   

Thanx,
Marcel
--------------------------------------------------------------------- To
     

unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
   

     

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]