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.
-David
