[jbosstools-issues] [JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina reassigned JBIDE-22878:
-------------------------------------

    Assignee: Rob Stryker  (was: Martin Malina)


I followed the steps with devstudio 10.2 nightly and EAP 6.4.

>From reading through the JIRA, the issue seems to be that we expect the deployed test-ear.war to include simple-ejb.jar , but in reality it's called simple-ejb-1.5.0.jar . 

I could see exactly this in my testing - both the deployed ear and exported ear (using File -> Export -> EAR) contain simple-ejb-1.5.0.jar . Also, the server view shows that. And same for the Deployment tab of Server editor. But if I understand this correctly, what we actually expected was that the jar would simply be called simple-ejb.jar (which I can see in the deployment assembly), right?

> EAR deployed from DevStudio to EAP contains errorneously named ejbs
> -------------------------------------------------------------------
>
>                 Key: JBIDE-22878
>                 URL: https://issues.jboss.org/browse/JBIDE-22878
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.3.Final, 4.4.0.Final
>         Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
>            Reporter: Mikhail Kalkov
>            Assignee: Rob Stryker
>             Fix For: 4.4.2.AM2
>
>         Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip
>
>
> I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
> When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
> This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing!



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)