-
1. Re: Structure of the exported EAR file (missing lib dir)
maxandersen Jun 19, 2008 6:55 AM (in response to gackonac)if you sayit works fine from within eclipse, where is the problem then ?
-
2. Re: Structure of the exported EAR file (missing lib dir)
gackonac Jun 19, 2008 7:22 AM (in response to gackonac)The problem is manual deployment (when put ear file into JBoss deployment dir). JBoss expect to find libraries in $EAR_ROOT/lib dir, not in $EAR_ROOT. In other words, I cant get proper "proper structured" ear file.
-
3. Re: Structure of the exported EAR file (missing lib dir)
maxandersen Jun 19, 2008 7:27 AM (in response to gackonac)You write "deployment works fine from within Eclipse" but say you cant get a proper ear....
Then I assume you are not using Eclipse to do the deployment....what are you using to deploy ? -
4. Re: Structure of the exported EAR file (missing lib dir)
gackonac Jun 19, 2008 7:45 AM (in response to gackonac)Ok, I'll try to be more clear:
I use Eclipse/JBoss tools for development. During that phase I deploy app by Eclipse. After that I need to deploy app on some other (test/stage) server. That need to be done manually. In order to create EAR file (to be used during manual deployment) I tried to use Eclipse (of course, building script can do the same). But exported EAR file (that is produced by Eclipse "export" action) is not proper structured (libraries are not within "lib" dir, but in the root of ear file). -
5. Re: Structure of the exported EAR file (missing lib dir)
maxandersen Jun 19, 2008 8:37 AM (in response to gackonac)so you are saying the files deployed by WTP servers are correct (e.g. ear has a lib dir with jars in it)
But when you use File > Export > EAR you get a different structure ?
that sounds weird to me. -
6. Re: Structure of the exported EAR file (missing lib dir)
gackonac Jun 19, 2008 8:55 AM (in response to gackonac)Sorry for the previous post.
No, Eclipse/JBoss tools deploy application with same structure with only one difference: app is exploded. This how it looks like:
[app.ear]
|
+--[app.war]
|
+--[app.jar]
|
+--lib1.jar
|
+--lib2.jar
|
+-- ...
There is no lib dir, all libraries are within the ear root. And it works!? But when the same structure is deployed manually as EAR file, error will occur. -
7. Re: Structure of the exported EAR file (missing lib dir)
maxandersen Jun 19, 2008 8:58 AM (in response to gackonac)please report this in jira with an example project (a minimal one)
thanks -
8. Re: Structure of the exported EAR file (missing lib dir)
rob.stryker Jun 20, 2008 6:22 PM (in response to gackonac)do you have an example project that can reproduce this? thanks.
-
9. Re: Structure of the exported EAR file (missing lib dir)
maxandersen Jun 20, 2008 6:41 PM (in response to gackonac)fyi, I just tested and if I have EarContent/lib/jbpm.jar that file ends up in the server deployed in lib/jbpm.jar so we definitly needs to know what you are actually doing.
The only way I could see this "bug" happen is if you put the jar in EarContent/jbpm.jar and expected us to magically put them into /lib. We don't do that ;)