Thanks Scott. I just wanted to rephrase what you said to clarify. It is imperative that you do not include classes in both a war and jar in the same ear as they will be loaded by two different class loaders, thus causing the ClassCastException. If they are present only once in the ear, they will be loaded and available in the unified loader repository and the war will grab the loaded references when an attempt to load them from the war fails. You do not need to modify the jboss-service.xml file.
Now that I understand how JBoss class loading works, I find it preferrable to the Sun implementation, which required you to put the file in both the jar and war in order for it to work. Thanks for the help and the great product. Raj View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881102#3881102 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881102 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
