Hi Scott, I completely forgot about this posting...
I tested a while and it seems that the complete jboss-path is responsible for that issue. Maybe the classloaders do theirselves to create this error, I will check the used Classloaders and their order of usage... regards, Lutz View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859956#3859956 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859956 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
