I was thinking that a solution to the problem that MD now has due to the
layout changes that I made WRT relatives paths could be solved by
forcing users to be explicit about which path they which to use (ie. not
allowing relative paths).
To make this work we need to expose some system property access inside
of the *service.xml files... probably as an attribute value subst and an
element... for example:
<!-- this is everything under jboss-*/lib -->
<classpath codebase="${jboss.home.dir}/lib" archives="*"/>
<!-- This is everything under jboss-*/server/<config>/lib -->
<classpath codebase="${jboss.server.home.dir}/lib" archives="*"/>
<!-- This would set the MyConfigName attribute to the servers config name.
<attribute name="MyConfigName">
<property name="jboss.server.name"/>
</attribute>
Could also expose a element ot set a property:
<!-- Set a property myprop to some value -->
<setproperty name="myprop" value="somevalue"/>
Which could then be used in config elements later in the file...
And to finally solve the two lib problem... just more than one classpath
(if that isn't the case already):
<classpath codebase="${jboss.server.home.dir}/lib" archives="*"/>
<classpath codebase="${jboss.home.dir}/lib" archives="*"/>
This would prefer libs from inside jboss.server.home.dir/lib before
jboss.home.dir/lib
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development