Hi,

can you check in the logs that you don't have a tomcat message saying
"Offending ...." and mentioning the javaee-api-6.0-6-tomcat.jar file?
Tomcat may notice that the jar contains Java EE APIs and then decides to
ignore it.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Wed, Oct 29, 2014 at 12:01 PM, sapozal <[email protected]> wrote:

> I arrive to the conclusion that Tomee have a very serious problem in EJB
> container.
>
> I created a simple EJB, deployed into Tomee
> I created a very simple EJB client inside of DoGet of very simple Servlet
> and inserted this Servlet into another Tomcat
> thats what I get on invocation
> java.lang.NoClassDefFoundError: javax/ejb/EJBHome
>         java.lang.Class.forName0(Native Method)
>         java.lang.Class.forName(Class.java:264)
>
> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:63)
>
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
>
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
>         javax.naming.InitialContext.init(InitialContext.java:242)
>         javax.naming.InitialContext.<init>(InitialContext.java:216)
> and thats despite that both openejb-client-4.7.1.jar and
> javaee-api-6.0-6-tomcat.jar are in lib of tomcat-client.
> Seems that all topic with EJB invocation from servlet of another tomcat/
> Grails app is very problematic...
> any help? anything Im doing wrong?
>
>
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Cant-invite-EJB-from-another-Tomcat-tp4672650.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Reply via email to