Your making sense, but for the use cases your talking about I don't agree
with the use of system properties. Rather, file paths should be relative to
a
"filesystem" JNDI DirContext so that both the location and implementation
of the filesystem is abstracted out. System properties also require setup on
the target host that I would rather handle on the configuration service.
My view of net installs is that I run the same command line on each
install target host and I get a properly configured JBoss server without
needing to locally configure the target host environment.
This potentially requires an ability to take a base configuration and apply
a target host specific transformation. The install service would be a
JBoss servlet instead of a static web server that would handle the target
host transformations.
----- Original Message -----
From: Bill Burke
To: Jboss-Development@Lists. Sourceforge. Net
Sent: Monday, October 29, 2001 10:23 AM
Subject: [JBoss-dev] Using system properties in jboss.jcml would help net
boot
Hey,
I think it would be nice to be able to access system properties within
jboss.jcml or any other MBean XML descriptor. I think this would greatly
help the net-boot(--net-install) feature of JBoss 3.0. For example, Jetty
is packaged in a .sar in JBoss 3.0. In that sar is the MBean XML descriptor
that has a hardcoded path to Jetty's configuration file 'jetty.xml'. Since
it is hardcoded this sar file cannot be deployed from a net installation of
jboss. Instead of putting the url "../conf/default/jetty.xml" as the path
to jetty's configuration, I think something like
"${INSTALL_PATH}/conf/${CONFIG_DIR}/jetty.xml" would make things more
flexible. JBoss would set up the INSTALL_PATH and CONFIG_DIR on startup as
System Properties. Am I making any sense?
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
