[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

[Max Andersen (JIRA)]

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

Max Andersen commented on JBAS-8754:
------------------------------------

1) Having duplicate jars on the classpath is not an uncommon thing; its used for overloading in many places but also its a challenge for many IDE's / build tools to keep clean because of inconsistent metadata - and there is a simple rule to handle this: Only look at the first class you find; and in this case it is literally the same file.

We had the same problem in Seam 2.x where they suddenly exploded because a class was found twice because of how Seam's hot deployment works + Eclipse packaging it causes double listng of classes - again solution was to ignore those found later in the classpath/classloader.

I completely understand it is not recommended but why is the app server not obeying ancient old classpath resolution mechanisms ?

2) Yes, the .classpath file defines this but these contains references to a classpath container that reads the manifest.mf files of the related project to avoid users to specify things twice.
And unfortunately Eclipse has a problem too with lib directories and manifest.mf in the sense that it uses the manifest.mf to find the classpath for ejb jars inside an EAR requiring us to list
it in manifest.mf to not have problems there (which is fine since it literally is the *same* jar)

If this is really how AS 6 wants to behave then thats gonna be tough/impossible to support :(


> 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