i finally found where this strange acting comes from. it's actually the contrary of
your suggestion. defining a loader repository is the cause of the problem, and when i
don't define any, the cast of the object accessed by jndi in the local interface of my
EJB is going perfectly well.
the unifiedClassLoader originally defined in my ear is for jboss seam. unfortunatelly, the
jar of seam is inside my ear. I didn't create the project, i'm just working on it
so i don't know the fundamentals of seam usage and how to deploy correctly a project
using it, but for now, the elimination of the <loader-repository> definition in
jboss-app.xml is causing the malfunction of jboss seam. i will continue to use the
reflection API for now while looking in the seam documentation a manner to deploy it with
my project without defining a loader repo in my ear (deploying it ini the jboss libdir for
exemple.. or in a separate app, maybe....)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148526#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...