The key is the elementFormDefault="unqualified" flag in the wsdl. Is this wsdl generated from the service? Is that flag different when run from within Eclipse as compared to standalone? With it unqualified, the error message is 100% correct. That element needs to be unqualified. Not sure why it would be working in Eclipse unless a different wsdl is being used/generated.
If this is a "wsdl first" case, definitely check that the proper wsdl is being used, the code is properly being generated from the wsdl, and also that the packaging for the service is properly adding all the package- info.class files into the packaging. You can also try adding -xjc-npa flag to the wsdl2java command to make it less reliant on the package- info.java stuff. Dan On Thursday, April 12, 2012 04:43:41 AM prashi11 wrote: > Thanks Alex O'Ree for giving time to this post. > Although I have already mentioned about the classpath and fiddler in my > earlier mail. > Initially I have also thought it could be a classpath issue, then I set > the same classpath for batch file which has been set for eclipse. Also, I > have used fiddler to capture the request, the request from the DotNet > client is same as I was sending for eclipse, that is, the requests are > identical. > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Calling-java-service-from-DotNet-client-g > etting-unmarshal-exception-tp5631860p5635397.html Sent from the cxf-user > mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
