"bstansberry(a)jboss.com" wrote : OK, with that approach presumably you could have some logic somewhere that says "if my metadata says I'm using JK, then check for jvmRoute metadata" which defaults to the overall server id. | | Is having jbossweb completely driven by web container metadata something you're thinking about for AS 5.0.0? If not, then my original question about whether it's OK to add a std jvmRoute attribute to server.xml still stands. No, it won't be completely rewritten by that timeframe. Its ok to refer to a system property for now. In the future there should be a jvmRoute setting that could default to the system property if not set. This ultimately would be a lookup against the metadata repository to see if had been mapped onto another value, coming from deployment metadata, annotations, system property, server settings, etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098982#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...