Hi James, I think it might be most appropriate to use the WS-Security standard and encrypt your payload. This can be done with most toolkits supporting WS-Security, but if yours does not, you can try a JAX-RPC Handler to remove content from the SOAP payload.
Additionally, you could try removing the element via the XMLCursor APIs before sending it, or develop an extension that handles its removal. -Jacob Danner On 5/4/07, James Snook <[EMAIL PROTECTED]> wrote:
I have a schema for a web service I'm developing. One of the fields in the schema contains sensitive information, credit card # for example. I need to prevent this field from being returned via the toString() and/or xmlText() methods. Has anyone else handled this? What's the easiest way to do this? James
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
