On Fri, Feb 06, 2004 at 09:05:23AM -0500, Dwight Shih wrote: > David, > > With the -m and -c options, deploy always uses OPENEJB_HOME/beans as the > target directory for the deployed jar (ignoring any deployments entries > in the config file). I've got a patch in progress to use the first > existing deployments directory in the config file instead, falling back > on OPENEJB/beans if there is no such directory.
Now I get what you were saying. This isn't exactly what you want, but... the deploy tool will leave your conf file untouched if it finds a <Deployments dir...> entry that matches. For example, if you have <Deployments dir="foo"> in your conf file and you execute the following command... openejb deploy foo/myEjbs.jar ... the deploy tool will not modify your config file. Again, it's not exactly what you want as it doesn't move the jar file for you. You are allowed to have as many <Deployments dir...> entries in your conf file as you like, not sure how we would choose which directory to move the jar into if we changed the meaning of the -m/-c. Any thoughts? > The -d option does a System.setProperty( "openejb.home", "blah, blah, > blah" ). If you follow the trail to > org.openejb.alt.config.ConfigUtils.searchForConfiguration, you'll see > that the config file is resolved relative to > org.openejb.util.FileUtils.getBase(). Since that references a static > class member, the System.setProperty doesn't happen soon enough. I'll have to take a look at that. I think this problem might just go away as Jacek added some great code (org.openejb.util.Launcher) that changes the way the deploy tool and others are run from the command line. -David > On Tue, 3 Feb 2004 18:56:56 -0500, [EMAIL PROTECTED] said: > > On Tue, Feb 03, 2004 at 07:17:54PM -0500, Dwight Shih wrote: > > > As far as I can tell, deploy always uses OPENEJB_HOME/beans as the target > > > directory when supplied with a configuration file defining a Deployments > > > directory (and when using -d to specify an alternate openejb.home for > > > that matter). Is this simply historical or is there a reason? > > > > > > > Hi Dwight, > > > > Not sure I follow exactly, but I can confirm what the tool should be > > doing. If you leave off the -m or -c options the bean should be > > deployed right were it is and not moved anywhere. Also, the conf file > > you deploy against should automatically be updated to have the full > > path of the bean added as a <Deployments ..> element. > > > > The -d *should* set the openejb.home, having the effect that the conf > > file be resolved relative to it. > > > > If there is a bug, or even something bothersome, I'd like to see it > > fixed. Let us know. > > > > -David > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > http://OpenEJB.sf.net > OpenEJB-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/openejb-user ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ http://OpenEJB.sf.net OpenEJB-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openejb-user
