y EJB of the WAR.
Do you have any idea why is this happening?
The only thing that I suspect is the JBoss Modules, which have changed the
Classloading procedure in JBoss.
Notes: The prefix "java:module/" before EJB name ("
java:module/MyEJBServiceImplName") is correct. This is h
roblem. I will try the "container
specific deployment configuration file" solution, and afterwards I will
communicate with JBoss guys to check what is going on here. I am pretty sure
that JBoss Modules magic has a few problems here (bugs are everywhere, even
in my room :) ).
Claus
