[ http://jira.jboss.com/jira/browse/JBAS-874?page=history ]

Scott M Stark updated JBAS-874:
-------------------------------

    Comment: was deleted

> XML in jar prevents deployer from adding it to classpath
> --------------------------------------------------------
>
>          Key: JBAS-874
>          URL: http://jira.jboss.com/jira/browse/JBAS-874
>      Project: JBoss Application Server
>         Type: Bug
>     Versions: JBossAS-3.2.6 Final
>     Reporter: SourceForge User
>     Assignee: Scott M Stark

>
>
> SourceForge Submitter: anajavi .
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to