[jboss-as7-dev] Do you need property substitutions in XSLT-augmented configs?

Kabir Khan kabir.khan at jboss.com
Tue Feb 21 05:29:07 EST 2012


In the testsuite, either is fine (unless we have some tests checking the model for expressions).
However, rather than performing the xslt mentioned to change the ports it sounds simpler to supply the properties when running the tests, e.g.
>      <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

and -Djboss.management.native.port=<new-value>

On 21 Feb 2012, at 07:07, Ondrej Zizka wrote:

> Currently, during XSLT transformation,
> 
>      <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
> 
> becomes
> 
>      <socket-binding name="management-native" interface="management" port="<new-value>"/>
> 
> Is it ok or do you need it to be
> 
>      <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:<new-value>}"/>
> 
> ?
> 
> Ondra
> 
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev




More information about the jboss-as7-dev mailing list