Hey All, has anyone of you ever overcome this error? Is it fixed in the latest JBoss version? Unfortunately we're still using 3.2.1 and haven't found a workaround for it yet.
Thanks, Stefan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875609#3875609 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875609 ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
