Sorry for this late response... But I've had time to test Jboss-3.2.3 only today! The same problem I had told you before still happens in this version, unfortunately :-( The workaround, to use Axis 1.1 in Jboss 3.2.1, was to put the Axis directory into deploy... I intend to migrate Jboss to 3.2.3... but with this problem, I'm not sure if it is stable enough...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828799#3828799 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828799 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
