I read it, I believe the solution in that post is to deploy war as part of ear for ejb interface internal referencing with packaging them in the war file 'coz war can share the context with ear after deployed.
I don't understand why with JBOSS 4.0.2 and onwards, having EJB interfaces included in war will cause problems, probably it's because it will lead JBOSS server in referencing some different stub class which is used when comipiling the EJB interfaces but not valid on the server-side context. But in my case, we may deploy the war and ear seperately for some reason. so I cannot put the war in the ear, and the EJB interfaces stay in the war file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076003#4076003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4076003 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
