Per the spec, load-api.jar does not have any visibility into classes within webapp.war. So the correct solution is to place the properties file outside of the WAR file. You can place it into its own JAR file, or into load-api.jar or myejb.jar, whichever works best.
There are some settings that can change this. In 5.1.0, in server/xxx/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml look for useJBossWebLoader and java2ClassLoadingCompliance within the WarDeployer bean. Of course, employing this solution is JBoss AS-sepcific and will not apply to other app servers (though they might have alternate mechanisms to do this).
You never said which version of JBoss AS you are using so if it is not 5.1.0 I'll leave it to you to find the file containing the settings. Grep is your friend...
Thank you for your reply.
I believe what I found is part of something bigger.
I've opened a new thread message with more detailed info and some source code included ... I really need to get over the situation, could you at least take a look at it?
I know the message is long ... but it would be nice if you could take a look.
I'm really needing to get over the situation, as the main project is holding back because of this logging failed situation, which I believe may have something to do with classloaders, classpaths, common libs in JBoss, or something else ...