I am moving an application from WebSphere to JBoss. Not being familiar with the SA tasks of JBoss, I have hit a question (and can't seem to find the answer on the net)...
I have a properties file that is located in the classpath of the application. This properties file must exist outside of the EAR since it contains different values on different servers (dev, test, prod).
How do I configure the deployment of the EAR to add a directory (which would contain the properties file) to add it to the application's classpath?
In WebSphere 5, it used the concept of a Shared Library (which would contain the directory name) and this was added to the application (and therefore part of the application's classpath).
I'm not sure that the topic of that link is what I am looking for. It appears that the link is talking about how to set system properties for JBoss (or properties that will be available to all applications running on that JBoss server).
I am looking for a way that my application (and preferably ONLY my application) running on a JBoss server will have access to a properties file. In addition, I don't want to have to specify the location of the properties file in my source code ... it should be found as part of the classpath (but not contained in the EAR / WAR / JAR).