[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=13285049#comment-13285049 ] 

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

I am not able to replicate this.  

When I import the attached project, if I right-click the ear project, go to properties, and go to "Deployment Assembly", we can see that the ejb has a name set for it. When I publish, that is the name I see in the resultant output ear: simple-ejb.jar. I will admit that sometimes the UI still references simple-ejb-1.5.0.jar   but that is because those portions of the UI don't have the context to know whether the ear is in a standalone mode or part of an EAR, and I doubt this can be fixed. 

Are you sure your environment has m2e-wtp installed? 

Also, JBIDE-18697 is unrelated to this and was found to have been caused by an openjdk bug regarding file locking in the application server itself. 

[~mmalina] Can you replicate this bug? 

> 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.1.Final
>
>         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)