Typically so does the jaxrpc based imlementations on a servlet. At this point we don't want to be committed to a full J2EE server, unless we have too. I am also wanting to stay pretty portable across the app servers.
At this point, given many of the other shortcomings that we have ran into with bugs, I think it will be easier to use GlassFish or the Sun App Server. They both resolved the three seperate bugs that we were waiting on. including this issue. In the end I want to ensure our war files can run on any of the app servers. Tomcat and Axis are not there, which is why JBoss split off. I think JBoss WS is just early in it's lifecycle and will work these issues out as well. I do appreciate the idea, we had considered it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922069#3922069 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922069 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
