By default, JBoss assumes that the location of all servers is ${JBOSS_HOME}/server. When config files try to reference something inside a particular server, they do so using the ${jboss.server.home.dir} which incorrectly points to ${JBOSS_HOME}/server/<instance> instead of /var/lib/jboss/<instance>. For example, in /deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml you might reference a keystore file for doing SSL and HTTPS by keystoreFile="${jboss.server.home.dir}/conf/my.keystore". My question is, should JBoss be patched to handle this, and does that affect anything else that might use that runtime variable? Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 43156 [details] jboss 3.2.3 ebuild and related files I have replaced all instances of the jboss runtime variable ${jboss.server.home.dir} with there proper "gentoo" paths.
marking as later, reference added to the tracker: also see #81038
reopen
These problems should go away when jboss is fixed to comply with the Java policy of not using bundled jars. Jboss probably won't be touched much until that happens, so marking it as duplicate. *** This bug has been marked as a duplicate of 63258 ***
