[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openejb-development
Subject:    Re: Hotdeploy/Undeploy
From:       David Blevins <david.blevins () visi ! com>
Date:       2007-07-13 1:58:37
Message-ID: EBD46475-3BF1-4E70-AAFF-619121EE9849 () visi ! com
[Download RAW message or body]


On Jul 2, 2007, at 3:12 PM, David Blevins wrote:

>
> On Jun 5, 2007, at 6:24 PM, David Blevins wrote:
>
>>
>> On Jun 4, 2007, at 10:21 AM, Karan Malhi wrote:
>>
>>> I was thinking about the following:
>>> the CLI deploy option uses the org.apache.openejb.config.Deploy.  
>>> I was
>>> thinking if somehow this object could use the
>>> org.apache.openejb.VmDeploymentManager. This way our CLI will be  
>>> able
>>> to use the JSR-88 compliant interfaces for its deployment. The same
>>> logic used here could be re-used in a swing, web or IDE based
>>> administrative console application. I have tried to look through the
>>> code, but didnt have enough time to be able to view it thoroughly. I
>>> will give this a try if you feel this is a valid option.
>>
>> I think that'd be a great thing to have.
>
> So I'm looking into the command line deploy functionality and  
> hoping to get something plumbed in in a short amount of time.  I  
> was thinking we'd use a variation on this idea.  Basically, we  
> would check to see if we can connect to the server and if so we'd  
> deploy via the Deployer ejb which is what the VmDeploymentManager  
> uses.
>
> If we can't connect to the server then we could just add a  
> Deployments entry to their openejb.xml or maybe just copy the  
> archive into the apps/ dir if they have one  and print a message  
> saying they've deployed offline and the app should be picked up  
> when openejb is started.

Ok, I just checked in a first run that should be pretty solid.  I  
tested what things looked like when deployment failed, when  
validation failed, when you tried to deploy an app that was already  
deployed, when you tried to deploy an app that contained a  
deploymentid already in use, etc.  After successful deployment it  
also lists all the app clients, persistence units, ejb-jars, ejbs,  
and even the jndi names for the ejbs.

I'll try and get some documentation together for it tomorrow with  
some sample output.

We should be in good shape for release.

-David

[prev in list] [next in list] [prev in thread] [next in thread]