7:13 a.m.
Michael Rootman created AS7-4100:
------------------------------------
Summary: EJB 2.1 entities are not deployed
Key: AS7-4100
URL: https://issues.jboss.org/browse/AS7-4100
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.Final
Environment: Jboss 7.1 Final, Windows 7, JDK 7
Reporter: Michael Rootman
Assignee: jaikiran pai
EJB 2.1 entities are not deployed on Jboss 7.1
1.Create jar file with 2.1 entities jar from integration examples:
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/bas...
2.Pack jar into EAR file.
3.Deploy EAR in standalone mode and watch, that JBoss recognized packed jar file and
confirms it deployment. No mentioning of recognized entities and binding them to JNDI
names
4.Trying to lookup entities on module or application level throws NameNotFoundException
P.S Adding EJB 2.1 Session beans to jar shows, that session beans recognized, deployed and
accesable for JNDI lookup.
Entity beans are not deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:01 a.m.
[
https://issues.jboss.org/browse/AS7-4100?page=com.atlassian.jira.plugin.s...
]
jaikiran pai resolved AS7-4100.
-------------------------------
Resolution: Rejected
You have to use the standalone-full configuration or standalone-full-ha configuration for
entity beans deployment in AS7. Start the server using:
{code}
./standalone -server-config=standalone-full.xml
{code}
and you'll see the entity beans being bound to JNDI:
{code}
14:28:37,154 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC
service thread 1-2) JNDI bindings for session bean named SimpleEJBWithOptionA in
deployment unit deployment "cmp2-simple.jar" are as follows:
java:global/cmp2-simple/SimpleEJBWithOptionA!org.jboss.as.test.integration.ejb.entity.cmp.simple.Simple
java:app/cmp2-simple/SimpleEJBWithOptionA!org.jboss.as.test.integration.ejb.entity.cmp.simple.Simple
java:module/SimpleEJBWithOptionA!org.jboss.as.test.integration.ejb.entity.cmp.simple.Simple
java:global/cmp2-simple/SimpleEJBWithOptionA!org.jboss.as.test.integration.ejb.entity.cmp.simple.SimpleHome
java:app/cmp2-simple/SimpleEJBWithOptionA!org.jboss.as.test.integration.ejb.entity.cmp.simple.SimpleHome
java:module/SimpleEJBWithOptionA!org.jboss.as.test.integration.ejb.entity.cmp.simple.SimpleHome
{code}
EJB 2.1 entities are not deployed
---------------------------------
Key: AS7-4100
URL: https://issues.jboss.org/browse/AS7-4100
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.Final
Environment: Jboss 7.1 Final, Windows 7, JDK 7
Reporter: Michael Rootman
Assignee: jaikiran pai
EJB 2.1 entities are not deployed on Jboss 7.1
1.Create jar file with 2.1 entities jar from integration examples:
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/bas...
2.Pack jar into EAR file.
3.Deploy EAR in standalone mode and watch, that JBoss recognized packed jar file and
confirms it deployment. No mentioning of recognized entities and binding them to JNDI
names
4.Trying to lookup entities on module or application level throws NameNotFoundException
P.S Adding EJB 2.1 Session beans to jar shows, that session beans recognized, deployed
and accesable for JNDI lookup.
Entity beans are not deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:56 a.m.
[
https://issues.jboss.org/browse/AS7-4100?page=com.atlassian.jira.plugin.s...
]
Michael Rootman closed AS7-4100.
--------------------------------
Solution provided and confirmed.
Thank you.
EJB 2.1 entities are not deployed
---------------------------------
Key: AS7-4100
URL: https://issues.jboss.org/browse/AS7-4100
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.Final
Environment: Jboss 7.1 Final, Windows 7, JDK 7
Reporter: Michael Rootman
Assignee: jaikiran pai
EJB 2.1 entities are not deployed on Jboss 7.1
1.Create jar file with 2.1 entities jar from integration examples:
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/bas...
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/bas...
2.Pack jar into EAR file.
3.Deploy EAR in standalone mode and watch, that JBoss recognized packed jar file and
confirms it deployment. No mentioning of recognized entities and binding them to JNDI
names
4.Trying to lookup entities on module or application level throws NameNotFoundException
P.S Adding EJB 2.1 Session beans to jar shows, that session beans recognized, deployed
and accesable for JNDI lookup.
Entity beans are not deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4670
days inactive
4674
days old
2 comments
2 participants
participants (2)
-
jaikiran pai (JIRA) -
Michael Rootman (JIRA)