5:24 p.m.
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
I'm having 2 different EARs and stateless session beans of the 2nd EAR are referencing
stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:28 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[ http://jira.jboss.com/jira/browse/EJBTHREE-1434?page=all ]
Juergen Zimmermann updated EJBTHREE-1434:
-----------------------------------------
Attachment: src.zip
hska.ear.zip
testHska.ear.zip
src.zip with the sources
hska.ear.zip with exploded ear #1
testHska.ear.zip with exploded ear #2
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:43 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[ http://jira.jboss.com/jira/browse/EJBTHREE-1434?page=comments#action_1242... ]
Andrew Lee Rubinger commented on EJBTHREE-1434:
-----------------------------------------------
A note that JDK6 is not yet supported.
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assigned To: Andrew Lee Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:43 p.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[ http://jira.jboss.com/jira/browse/EJBTHREE-1434?page=all ]
Andrew Lee Rubinger reassigned EJBTHREE-1434:
---------------------------------------------
Assignee: Andrew Lee Rubinger
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assigned To: Andrew Lee Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:28 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[ http://jira.jboss.com/jira/browse/EJBTHREE-1434?page=comments#action_1242... ]
Juergen Zimmermann commented on EJBTHREE-1434:
----------------------------------------------
Here are the log records in server.log when deploying the 2nd EAR:
2008-07-09 19:24:53,084 WARN
[org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (HDScanner) Unresolved
references exist in
JBossMetaData:[testHskaEJB.jar#KundenverwaltungTestBean:AnnotatedEJBReferenceMetaData{name=kvProxy,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
de.hska.kundenverwaltung.Kundenverwaltung}]
2008-07-09 19:24:53,154 INFO [STDOUT] (HDScanner) ======> Creating interceptor
metadata bridge
2008-07-09 19:24:53,244 WARN [org.jboss.injection.EJBRemoteHandler] (HDScanner)
EJBTHREE-1289: Using legacy EjbEncInjector, because mappedName for enc
"env/de.hska.test.KundenverwaltungTestBean/kvProxy", field "kvProxy"
is null (container.environmentRefGroup.annotatedEjbReferences =
[AnnotatedEJBReferenceMetaData{name=kvProxy,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
de.hska.kundenverwaltung.Kundenverwaltung}])
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Created
KernelDeployment for: testHskaEJB.jar
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
installing bean:
jboss.j2ee:ear=testHska.ear,jar=testHskaEJB.jar,name=KundenverwaltungTestBean,service=EJB3
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with
dependencies:
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and
demands:
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
Class:de.hska.kundenverwaltung.Kundenverwaltung
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jboss.ejb:service=EJBTimerService
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and
supplies:
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
Class:de.hska.test.KundenverwaltungTestRemote
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jndi:testHska/KundenverwaltungTestBean/remote-de.hska.test.KundenverwaltungTestRemote
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jndi:KundenverwaltungTestBean
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jndi:testHska/KundenverwaltungTestBean/remote
2008-07-09 19:24:53,254 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added
bean(jboss.j2ee:ear=testHska.ear,jar=testHskaEJB.jar,name=KundenverwaltungTestBean,service=EJB3)
to KernelDeployment of: testHskaEJB.jar
2008-07-09 19:24:53,495 INFO [org.jboss.ejb3.EJBContainer] (HDScanner) STOPPED EJB:
de.hska.test.KundenverwaltungTestBean ejbName: KundenverwaltungTestBean
2008-07-09 19:24:53,495 ERROR
[org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error
installing to Start:
name=jboss.j2ee:ear=testHska.ear,jar=testHskaEJB.jar,name=KundenverwaltungTestBean,service=EJB3
state=Create
java.lang.NullPointerException
at
org.jboss.ejb3.proxy.factory.ProxyFactoryHelper.getRemoteAndBusinessRemoteInterfaces(ProxyFactoryHelper.java:617)
at
org.jboss.ejb3.proxy.factory.ProxyFactoryHelper.getJndiName(ProxyFactoryHelper.java:421)
at org.jboss.ejb3.Ejb3Deployment.getEjbJndiName(Ejb3Deployment.java:377)
at org.jboss.ejb3.EJBContainer.getEjbJndiName(EJBContainer.java:1427)
at org.jboss.injection.EjbEncInjector.inject(EjbEncInjector.java:80)
at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:855)
at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:185)
at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:202)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56)
at
org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110)
at
org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at
org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
at
org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:624)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:442)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:88)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:991)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1023)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
2008-07-09 19:24:53,735 WARN [org.jboss.system.server.profileservice.hotdeploy.HDScanner]
(HDScanner) Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS IN ERROR: Name -> Error
jboss.j2ee:ear=testHska.ear,jar=testHskaEJB.jar,name=KundenverwaltungTestBean,service=EJB3
-> java.lang.NullPointerException
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:676)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assigned To: Andrew Lee Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:31 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[
https://jira.jboss.org/jira/browse/EJBTHREE-1434?page=com.atlassian.jira....
]
Juergen Zimmermann commented on EJBTHREE-1434:
----------------------------------------------
I retried with JDK 1.5.0_16-b02 and still get this warning (and following errors):
WARN [MappedReferenceMetaDataResolverDeployer] Unresolved references exist in
JBossMetaData:[testHskaEJB.jar#BestellverwaltungTestBean:AnnotatedEJBReferenceMetaData{name=bvProxy,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
de.hska.bestellverwaltung.Bestellverwaltung},
testHskaEJB.jar#KundenverwaltungTestBean:AnnotatedEJBReferenceMetaData{name=kvProxy,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface
de.hska.kundenverwaltung.Kundenverwaltung}]
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assignee: Andrew Lee Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:56 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[
https://jira.jboss.org/jira/browse/EJBTHREE-1434?page=com.atlassian.jira....
]
Juergen Zimmermann commented on EJBTHREE-1434:
----------------------------------------------
Are there any news?
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assignee: Andrew Lee Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:41 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[
https://jira.jboss.org/jira/browse/EJBTHREE-1434?page=com.atlassian.jira....
]
Andrew Lee Rubinger commented on EJBTHREE-1434:
-----------------------------------------------
Getting:
07:35:48,649 ERROR [AbstractKernelController] Error installing to Real:
name=vfsfile:/home/alrubinger/business/jboss/wc/jbossas/trunk/build/output/jboss-5.0.0.CR2/server/default/deploy/hska.ear/
state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying hskaEJB.jar: Unexpected error
during load of: de.hska.kundenverwaltung.KundenverwaltungBean, msg=Bad version number in
.class file
Also, the attached deployables are not proper EARs, JARs.
The implementation referenced in the error stacktrace of this ticket has changed, so
I'd like to run this case through.
Please either:
1) Provide slimmed-down proper deployables attached to this JIRA
2) Test on AS trunk from SVN:
$> svn co http://anonsvn.jboss.org/repos/jbossas/trunk
$> cd trunk/build
$> ./build.sh
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assignee: Andrew Lee Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:49 a.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[
https://jira.jboss.org/jira/browse/EJBTHREE-1434?page=com.atlassian.jira....
]
Juergen Zimmermann resolved EJBTHREE-1434.
------------------------------------------
Resolution: Rejected
ejb-jar.xml has to be extended for the 2nd ear so that the beans of the 1st ear are
declared by using the tags ejb-name and ejb-class
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assignee: Andrew Lee Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work
[
https://issues.jboss.org/browse/EJBTHREE-1434?page=com.atlassian.jira.plu...
]
ram snaps commented on EJBTHREE-1434:
-------------------------------------
Was this issue ever fixed, we also are running into this same issue when we upgraded JBoss
from 4.x to 5.1. Can someone please confirm?
5.0.0CR1: EJB refs across EARs don't work
-----------------------------------------
Key: EJBTHREE-1434
URL: https://issues.jboss.org/browse/EJBTHREE-1434
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: JBoss 5.0.0.CR1, JDK 6u10beta
Reporter: Juergen Zimmermann
Assignee: Andrew Rubinger
Attachments: hska.ear.zip, src.zip, testHska.ear.zip
I'm having 2 different EARs and stateless session beans of the 2nd EAR are
referencing stateless session beans of the 1st ear. It worked fine with 4.2.2
I'll attach a stripped down testcase:
* src.zip: source of projects for Eclipse w/ JBoss Tools
* hska.ear.zip: exploded EAR 1 (and zipped for transferring)
* testHska.ear.zip: exploded EAR 1 (and zipped for transferring)
src.zip:
* hska is the 1st EAR project
* hskaEJB contains the ejb module for hska
* testHska is the EAR project for the 2nd EAR
* testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB
* testHskaClient is an application client module for testHska using JUnit
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4871
days inactive
5831
days old
9 comments
3 participants
participants (3)
-
Andrew Lee Rubinger (JIRA) -
Juergen Zimmermann (JIRA)
-
ram snaps (JIRA)