I'm trying to test out porting a pretty simple EAR from WebLogic to JBoss. I have an EJB JAR, a bunch of "library" JARs (like Quartz), and a WAR.
In WebLogic, putting things like the quartz.properties, or my own app's .properties file in /APP-INF/classes made them available, and I understand that's a WebLogic-specific idiom.
When I move my properties files to the root of the ear, when I deploy, my EJB's deploy, but my startup code fails, trying to load the quartz. properties file with :
10:24:17,747 ERROR [SchedulerFactory] Properties file: 'file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp745app.ear!/quartz.properties' could not be read.
org.quartz.SchedulerException: Properties file: 'file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp745app.ear!/quartz.properties' could not be read.
[See nested exception: java.io.FileNotFoundException: file:\C:\jboss-4.0.2\server\default\tmp\deploy\tmp745app.ear!\quartz.properties (The filename,
directory name, or volume label syntax is incorrect)]
I don't understand this; there IS no directory named "tmpxxxapp.ear!" in the \tmp\deploy directory.
I know I can do things with the MANIFEST.MF file and class paths, but if I'm just using pre-built JARs like for Quartz, I would really rather not edit them.
It looks like it's close to working; why am I getting these file not found exceptions???
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
Read the spec.
Nothing in the root of an ear is ever added to the classpath.
It is just a holder/consolidator for other deployments.