Deployment dir is hard-coded. However, I'd bet it would be easy to
override the standard deployer. Grab the jboss source, make a class
MyDeployer that extends J2eeDeployer, reimplement the base class
initService() to preferentially pick up the deploy dir from an envvar,
make a trivial MyDeployerMBean like J2eeDeployerMBean, place the
MyDeployer classes in a jar in lib/ext, change jboss.jcml entry:
<mbean code="org.jboss.deployment.J2eeDeployer" ...
to
<mbean code="my.pkg.MyDeployer" ...
and let the magical jboss service architecture do the rest. Caveat is
that deployment is usually the private purview of the container; it's
probably bad form to build external dependencies on deployment location.
Classpath can be configured by changing the ClassPathExtension entries
in jboss.conf.
Above is true jboss 2.2 - 2.4. It looks like it will change a bit for
3.0.
Fred Loney
Spirited Software, Inc.
www.spiritedsw.com
----- Original Message -----
From: "Mica Cooper" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 21, 2001 2:36 PM
Subject: [JBoss-user] Path Configuration
> Problem:
> I need to config the paths for \lib\ext and \deploy to point to other
> directories. Is there a config that will allow me to have Jboss set
> additional directories for this?
>
> I have the Jboss paths like this
> c:\Jboss\lib\ext
> c:\Jboss\deploy
>
> and need to able to set them to ALSO use other dirs
>
> c:\project\mycompany\lib
> c:\project\mycompany\deploy
>
> Thanks in advance,
> Mica Cooper
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
