Rob Leland created TOMEE-4033:
---------------------------------
Summary: Unable to find EJB resource/class located in JAR file
during deployment
Key: TOMEE-4033
URL: https://issues.apache.org/jira/browse/TOMEE-4033
Project: TomEE
Issue Type: Bug
Components: TomEE Core Server
Affects Versions: 9.0.0-M9
Reporter: Rob Leland
Attachments: image-2022-09-07-16-23-33-363.png,
image-2022-09-07-16-44-59-713.png, stack-tomee-plus.log
An example application which does a EJB dependency lookup is failing in the
latest TomEE plus Nightly ,see attached stack trace.
This works in GlassFish 6.2.5.
When tomee finished this diagnostic error is printed:
{code:java}
Unknown Container Exception: java.rmi.RemoteException: Cannot read the response
from the server. The class for an object being returned is not located in this
system:; nested exception is:
java.lang.ClassNotFoundException: examples/stateless/DepartmentService
{code}
That class exists in a JAR in the WAR file:
!image-2022-09-07-16-44-59-713.png|width=835,height=313!
*To Reproduce*
The Application source can be found here and needs no configuration to run:
[https://github.com/free2create/pro-jakarta-persistence-jakarta-ee10]
To Build:
{code:java}
mvn clean package{code}
Then deploy the WAR file found at:
examples/Chapter3/08-dependencyLookup/servlet/target:
In TomEE the app fails during deployment
In GlassFish, navigate to:
URL:
[http://localhost:8080/ch3-08-dependency-servlet-1.0.0/DepartmentServiceServlet]
When the Audit button is pushed , you will see this.
!image-2022-09-07-16-23-33-363.png|width=888,height=189!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
