Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-6320

EAR deployment with option "as compressed archives" results in ear containing invalid jars

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.1.0.GA
    • Fix Version/s: 3.1.1, 3.2.0.M1
    • Component/s: archives
    • Environment:

      Windows XP Pro SP3, Java JDK 1.6.0_20, Eclipse IDE for JEE 3.5.2, JBoss Tools 3.1 (JBossAS Tools 2.1.0.v201003050540R-H56-GA), WTP Patches 3.1.2.v201003181725), m2Eclipse 0.10.0

    • Steps to Reproduce:
      Hide

      1. Create Enterprise Application Project (Target: JBoss6, EAR version 5.0, Generate application.xml)
      2. Create a lib folder at root level and a lib folder in EarContent
      3. Copy jboss-seam.jar into lib folder and mvel2.jar into EarContent/lib folder
      4. Add jboss-seam.jar as ejb-module in application.xml (<module><ejb>jboss-seam-2.2.1.CR1.jar</ejb></module>)
      5. Open Properties of JBoss6 Server in "Servers" view
      6. Go to the "Deployment" tab and activate the option "Deploy projects as compressed archives"
      7. Deploy project to JBoss6

      Show
      1. Create Enterprise Application Project (Target: JBoss6, EAR version 5.0, Generate application.xml) 2. Create a lib folder at root level and a lib folder in EarContent 3. Copy jboss-seam.jar into lib folder and mvel2.jar into EarContent/lib folder 4. Add jboss-seam.jar as ejb-module in application.xml (<module><ejb>jboss-seam-2.2.1.CR1.jar</ejb></module>) 5. Open Properties of JBoss6 Server in "Servers" view 6. Go to the "Deployment" tab and activate the option "Deploy projects as compressed archives" 7. Deploy project to JBoss6

      Description

      The deployment of a minimal Enterprise Application Project (consisting of e.g. jboss-seam.jar as ejb-module and mvel2.jar as 3rd-party jar) with the deployment option "Deploy projects as compressed archives" activated, results in an ear containing some invalid jars: These invalid jars are containing only one jar with the same name which finally contains the actual jar content.
      E.g. the mvel2.jar contains a mvel2.jar which contains the "META-INF" and an "org" directory.

      It seems that every supplied jar is affected that is determined as module jar, because it is an ejb-module (e.g. jboss-seam.jar) or its manifest contains a "Main-class" entry marking it as client-module.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rob.stryker Rob Stryker
                  Reporter:
                  gonne Gonne Martens
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: