Starting from some months ago, the JBossWS team is putting his main effort into JAXWS. However, you might create a minimal application reproducing this problem and attach it to a new Jira issue. This way somebody from the community may try to fix the potential bug into the codebase.
Apart from this, considering you're dealing with migration issues due to the AS upgrade, I would really suggest you to evaluate switching to jaxws (also upgrading to the latest jbossws release); here http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_vs_JAX-RPC you can find a brief introduction explaining why this might be a good idea. Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094951#4094951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094951 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
