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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-22878:
-------------------------------------

[~mkalkov] - There is a way to fix this. Please follow these steps instead:

* Download JBoss Developer Studio 10.0.0.GA
* Add JBoss EAP 6.4 runtime to the studio.
* Unzip attached test-project.zip into workspace
* In Studio, use import existing projects wizard to import test-ejb and test-ear projects into workspace
* Double-click the server in Servers view, select "Deployment" tab and check "Deploy projects as compressed archives"
* **Click in the table on the "Deployment Location" column for the module you wish to change the deployment name of, and make the change. This option is only available when the server is stopped and there are no modules added to the server adapter**
* Add test-ear to the server, right-click on the server and select "Clean".
* Now navigate to the deployments directory and inspect test-ear.ear contents. Compare this file to to test-ear.ear obtained from command-line maven build or via Export EAR Eclipse wizard.

> 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
>         Attachments: screendump.png, 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 and remember to revert this change before committing!



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