[jboss-jira] [JBoss JIRA] (WFLY-4318) Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy

[Geoffrey De Smet (JIRA)]

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

Geoffrey De Smet updated WFLY-4318:
-----------------------------------
    Description: 
Relates to WFLY-4081 and the IntelliJ issues to make using WildFly less of a pain in IntelliJ:
  https://youtrack.jetbrains.com/issue/IDEA-133729
  https://youtrack.jetbrains.com/issue/IDEA-95695

"Checked solution in IntelliJ 14.1. In general it works. But there is problem with exploded EAR deployments. If I'm trying to deploy exploded EAR which contains some EJB jar with several EJBs beans, this EJBs fails to start in JBoss EAP: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor doesn't even start. But if I try to deploy exploded EAR with ".ear" postfix (just an output folder with ".ear" on the end) it successfully starts EJB beans and I see some JNDI mapping to it from "org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor". Maybe this is a problem of JBoss EAP itself but it seems that we cannot use just a regular folder for exploded EAR output, we have to add ".ear" suffix on the end :("

"For exploded EAR we should still add ".ear" extension to the exploded directory. Otherwise all EJB beans wouldn't be processed and started after deploy."

  was:
Relates to WFLY-4081 and the IntelliJ issues to make using WildFly less of a pain in IntelliJ:
  https://youtrack.jetbrains.com/issue/IDEA-133729
  https://youtrack.jetbrains.com/issue/IDEA-95695

"Checked solution in 14.1. In general it works. But there is problem with exploded EAR deployments. If I'm trying to deploy exploded EAR which contains some EJB jar with several EJBs beans, this EJBs fails to start in JBoss EAP: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor doesn't even start. But if I try to deploy exploded EAR with ".ear" postfix (just an output folder with ".ear" on the end) it successfully starts EJB beans and I see some JNDI mapping to it from "org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor". Maybe this is a problem of JBoss EAP itself but it seems that we cannot use just a regular folder for exploded EAR output, we have to add ".ear" suffix on the end :("

"For exploded EAR we should still add ".ear" extension to the exploded directory. Otherwise all EJB beans wouldn't be processed and started after deploy."



> Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy
> ------------------------------------------------------------------------------------
>
>                 Key: WFLY-4318
>                 URL: https://issues.jboss.org/browse/WFLY-4318
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Geoffrey De Smet
>            Assignee: Brian Stansberry
>
> Relates to WFLY-4081 and the IntelliJ issues to make using WildFly less of a pain in IntelliJ:
>   https://youtrack.jetbrains.com/issue/IDEA-133729
>   https://youtrack.jetbrains.com/issue/IDEA-95695
> "Checked solution in IntelliJ 14.1. In general it works. But there is problem with exploded EAR deployments. If I'm trying to deploy exploded EAR which contains some EJB jar with several EJBs beans, this EJBs fails to start in JBoss EAP: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor doesn't even start. But if I try to deploy exploded EAR with ".ear" postfix (just an output folder with ".ear" on the end) it successfully starts EJB beans and I see some JNDI mapping to it from "org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor". Maybe this is a problem of JBoss EAP itself but it seems that we cannot use just a regular folder for exploded EAR output, we have to add ".ear" suffix on the end :("
> "For exploded EAR we should still add ".ear" extension to the exploded directory. Otherwise all EJB beans wouldn't be processed and started after deploy."



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)