I encountered the same problem here, using gsoap 2.7.6e for building the client app and the currenct cvs scheckout for JBoss 4.0.4.CR2. Most elements in the wsdl file are marked as nillable=true. The wsdl and the mapping file is generated with wscompile 1.6. The c++ variables are not set (==NULL), so the soap mesage doesn't include the element. The validation of the message in org.jboss.xb.* gives an error/excpetion that the element was not found in the xml fragment. Using JBoss 4.0.4.CR1 with org.jboss.axis.* the webservice communication worked perfect.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929902#3929902 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929902 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
