|Strange "deployment assembly" manifest editor behavior [message #666321]
||Tue, 19 April 2011 21:33
| Vadim Dmitriev
Registered: July 2009
I observe a strange "deployment assembly" properties page behavior. I
suspect it's to due my lack of knowledge regarding this 'JEE packaging'
theme. I'll be grateful for any clarification on the subject.
I have project 'testEAR' and it's child EJB project 'testEJB'. Here is
what I do when I observe this strange behavior I talk about.
testEAR -> properties -> deployment assembly -> add... -> archive from
file system. I selected 'openfaces.jar' and hit 'OK'. So now I have
openfaces.jar with deploy path "lib/openfaces.jar". "EAR library
directory" is "lib".
testEJB -> properties -> deployment assembly -> manifest entries ->
add... I see an empty list, though I suspect that "lib/openfaces.jar"
should be listed. Ok, open testEAR's deployment assembly again and
change "EAR library directory" to "lib1". Go back to testEJB deployment
assembly. Now I see "lib/openfaces.jar" in "Add manifest entries" list.
Is it OK that EAR libraries are not listed for inclusion into testEJB's
manifest when "EAR library directory" value is a prefix for libraries'
deployment paths? I can successfully add entries manually in deployment
assembly manifest editor even if jars are not listed, but it is not very
Powered by FUDForum
. Page generated in 0.01673 seconds