[jboss-jira] [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572179#comment-12572179 ] 

jaikiran pai commented on JBAS-8754:
------------------------------------

>> You need to be a bit more informative please since your comment is as confusing as the exception being thrown ;) 

Max, Ales recently fixed an issue in processing MANIFEST.MF file. If you now deploy the application attached to https://issues.jboss.org/browse/JBIDE-7932 against the latest AS nightly build, you will see a _relatively_ better error message about duplicate binding exception for the EJBs.

The problem is that the jboss-seam.jar (which has EJBs within it) gets listed twice, once in the application.xml and then again as a ClassPath element in the MANIFEST.MF of another EJB deployment. This leads to the EJBs in the jboss-seam.jar being deployed/processed twice. This has always been a problem (although it kept manifesting itself in different ways).

As Carlo points out from the spec:

JavaEE 6 EE.8.5.2 Bullet 4:
Note that the presence of component-declaring annotations in shared artifacts, such as libraries in the library directory and libraries referenced by more than one module through Class-Path references, can have unintended and undesirable consequences and is not recommended. 

The effect of having a jar (in this case jboss-seam.jar) containing component-declaring annotations (for example, EJB bean annotation like @Stateful ) referenced through Class-Path element of MANIFEST.MF can have undesired and unintended consequences and is not recommended.


>> if we "fix" this by removing the classpath entry in the manifest.mf Eclipse "looses" its ability to see what classes to compile against.

I'm not an IDE guy, so I don't know much, but I thought Eclipse uses the .classpath file to setup classpaths and not the MANIFEST.MF of the jar. Isn't that the case?



 

> EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-8754
>                 URL: https://issues.jboss.org/browse/JBAS-8754
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.0.CR1
>            Reporter: Max Andersen
>            Assignee: Shelly McGowan
>            Priority: Blocker
>
> As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss Tools seam tooling because it has an entry in its manifest.mf.
> This is a regression and will mean that seam projects (and possibly other ear projects) created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
> (but it will work on all previous AS versions)
> I consider that a blocking regression.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira