Hi, unfortunately I ran into the very same problem when using any of my web-services providing methods consuming "<complexType ..." arguments with nillable elements of any type.
My Environment: JBoss 4.0.4.GA (EJB3-RC8 patch and update to JBossWS 1.0.3 applied/) which takes any web-mehtod argument with nillable elements! The problem was introduced with the update to jbossws 1.0.3 (jbossws 1.0.2 had no problem with the very same server and client code) Before I start digging into the code or porting my services to a different web-service provider I would like to ask whethere there is any workaround/patch which could be applied until jbossws-1.1.0 for which the fix is scheduled is out? - downgrading to jbossws 1.0.2 is not an option due to other problems which were actually fixed with jbossws 1.0.3 - waiting until Oct. 31 (jbossws 1.1.0 release?) is also no option. Many Thanks, Bertl View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971108#3971108 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971108 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
