Well if jetty can do It I can't imagine it not working for you
not that I am aware of....
AFAIK the jetty attribute you show must have type Element, and parse the contents itself.
Can you be a little more specific about the functionality you want?
My grokking of this is that this is a guy coming from Jetty-world, where the XML configuration is just Java with XML syntax, to the JBoss world where we are more restrained.
Jetty let's you do stuff like :
Which will look for a setPort() method on the current object and call it with the result of System.getProperty("jetty.port"), or if that is null "8080".
This means that important configuration values may be externalised to the command line etc...
I am not aware of anything in our JMX config dialect that supports anything like this.
I am thoroughly aware that there is nothing like this in jboss mbean configuration. Basically I think this is a good thing. So far I think if you need non-constant sources for your attribute value you should be generating your *-service.xml file somehow with a tool (such as ant filtering or xsl processing) that will find and insert the values you want. I wouldn't mind reading other opinions, however.