Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

problem with classpath

 
Maciej Bajolek
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi *,
I need a help
(Question 1)
I have application which has some ejb modules. My EAR file looks like:
wms.ear/
config/
config.properties
META-INF/
application.xml
manifest.mf
jboss-app.xml
ejb-module.jar
I need to have file: config.properties in ejb-module.jar classpath (there is configuration of a module).
When I use WLS or OC4J, I add "Class-Path: config" entry to ejb-module.jar manifest.mf file and in my Config service I access file using getResourceAsStream("/config.properties") method.
Unfortunatelly in JBoss 3.2.1 I get following worning messages:
-
18:22:26,102 WARN [MainDeployer] The manifest entry in file:/C:/jboss/server/default/tmp/deploy/ser
ver/default/deploy/wms.ear/51.wms.ear-contents/mdb-ejb.jar references URL file:/C:/jboss/server/defa
ult/tmp/deploy/server/default/deploy/wms.ear/51.wms.ear-contents/config which could not be opened, entry ignored
-
Is there any other solution for it?
(Question 2)
As I mentioned before I use JBoss 3.2.1. How can I deploy my application using EXPLODED directory format. When I unpack EAR and all modules, change application.xml module entries pointing to directory (module) instead of jars/wars
I read that all I need is to unpack EAE ant its modules into JBoss's deploy directory ant everything will be ok.
It does not work!
Am I doing something wrong?
How can deploy application using Exploded directory format?
--
best regards
Maciek
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic