Stop Empty SOAP elements

[jizzoe]

Hi All,

I'm using JBoss WebServices with JAX-WS to connect to a Web Service. I use wsconsume to generate Java Classes.

Here's my dliema. In some of my generated classes that I'm using as request objects, I instantiate the object, populate some fields and send it along. Problem is all of those fields are getting generated in the SOAP message, even if I left it as null. On the Web Service side, it's been interpreted as empty string instead of NULL, which causes problems.

Any idea why null values still get generated in SOAP? And any idea hot to stop this from happening? These fields are defined as nillable in the WSDL.

Any help is greatly appreciated.

Thanks,

Joe

[asoldano]

Could you please capture a soap message exchange showing this and post it here along with the wsdl contract and the stack/version you're using both on client and server side?
Thanks