The problem is not really with JBoss wanting to start in a particular directory. The
problem is that some of the add-ons configurations are specified with respect to the
current directory. InstantDB is one such example. Instead of treating the directory
paths as relative to a classpath resource they are paths relative to the current 
directory.

Probably the simplest solution is to patch the service tool to allow for the 
specification
of a starting directory. Or look at another Java service tool that already has that
capability like this one: http://www.eworksmart.com/jnt/


----- Original Message ----- 
From: "Tom Cook" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Thursday, February 01, 2001 2:27 PM
Subject: Re: [jBoss-User] Starting as a service under NT?


> Errrmmmmm... I hate pointing the obvious out to competent people, but how about
> 'cd %JBOSS_HOME%' at the top of your batch file?
> 
> Tom
> 
> On Fri, 02 Feb 2001, you wrote:
> > Hi,
> > 
> >   We have recently replaced Weblogic with jBoss in a high profile
> > application.  We are very pleased with our results so far.
> > 
> >   We are preparing to enter testing with our application, and we have
> > been spending the past few days configuring our testing environment.  We
> > need to make jBoss start as a service under 2000.
> > 
> >   There are many packages around the web that promise to 'start any
> > executable as a service', and we have one of these up and running, using
> > a batch file to start jBoss.  But there is a very elegant package for
> > starting java programs as services we would like to use, located at
> > 
> > http://www.roeschter.com/index.html
> > 
> >   The problem we are having is that jBoss wants to start from a
> > particular directory (the jBoss/bin directory), and we can't really
> > control this when starting as a service.  We get a little farther when
> > we specify -Duser.dir=<path_to_jBoss_bin>, but now we fail when
> > instantdb is looking for a file.
> > 
> >   I guess the question I'm asking could be phrased a couple different
> > ways:  1) Is there a way to start jBoss in such a manner that it doesn't
> > care where you are launching it from?  if not, 2) is there a way to
> > specify (via a registry entry or something) the working directory for a
> > service under NT/2000?
> > 
> >   We are a group of pretty competent developers, and can contribute our
> > work back to jBoss...  based on the example from the service-starting
> > package above, we have a 'wrapper' that implements stoppable and starts
> > jBoss...  between that and the Free .exe file from that site, it would
> > make a nice add-on for jBoss when running in the (crippled) windows
> > NT/2000 environment.
> > 
> > 
> > -David Bock
> > Software Engineer,
> > FGM, inc.
> > 
> > 
> > 
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > List Help?:          [EMAIL PROTECTED]
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> List Help?:          [EMAIL PROTECTED]
> 
> 



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]

Reply via email to