[
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