Bugs item #891626, was opened at 2004-02-06 13:32
Message generated for change (Comment added) made by raja05
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866

Category: None
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Antti Lehto (anajavi)
Assigned to: Nobody/Anonymous (nobody)
Summary: XML in jar prevents deployer from adding it to classpath

Initial Comment:
Deployer does not add classes from manifest if jar
contains xml.

This behavior violates the j2ee 1.3 and 1.4 specification. 
The 1.3 spec says that container should add all classes
to classpath from jar.
The 1.4 spec says that container should ignore any xml
in jar's mentioned in manifest.

Here's how I found the problem:
I accidently jarred jboss.xml and ejb-jar.xml inside
some.jar's META-INF.

This some.jar was mentioned in MANIFEST.MF of a ejb-jar.

When deploying ejb-jar the deployer failed to add
some.jar to ejb-jar's classpath:
2004-01-30 15:36:14,814 DEBUG
[org.jboss.deployment.MainDeployer] new manifest entry
for sdi at some-ejb.jar entry is lib/some.jar
2004-01-30 15:36:14,822 DEBUG
[org.jboss.deployment.MainDeployer] using deployer
[EMAIL PROTECTED]
2004-01-30 15:36:14,823 DEBUG
[org.jboss.deployment.MainDeployer] The manifest entry
in
file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/some-ejb.jar/
references URL
file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/lib/some.jar
which could not be opened, entry ignored

It seems to me that deployer tried to deploy the
some.jar because of these xml-files. Jar was not added
to classpath after failing deployment.

I also think, that these DEBUG messages are misleading.
The jar-file could have been added to classpath,
although of failing deployment. It took quite time to
find the real problem.



----------------------------------------------------------------------

Comment By: Rajagopal Venkataraman (raja05)
Date: 2004-05-07 10:21

Message:
Logged In: YES 
user_id=206536

If this were to be delegated to the EJBDeployer which it
would given that there was a jboss.xml and ejb-jar.xml in
it, then the deployment shud have failed as the files
mentioned in that xml would not be available in the package. 
Can you attach a small example to illustrate ur problem so i
can reproduce it at my end?

Thanks
Raja


----------------------------------------------------------------------

Comment By: Rajagopal Venkataraman (raja05)
Date: 2004-05-07 10:20

Message:
Logged In: YES 
user_id=206536

If this were to be delegated to the EJBDeployer which it
would given that there was a jboss.xml and ejb-jar.xml in
it, then the deployment shud have failed as the files
mentioned in that xml would not be available in the package. 
Can you attach a small example to illustrate ur problem so i
can reproduce it at my end?

Thanks
Raja


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to