Thanks Chris. Now I it can be done I just have to figure out how. Does anyone have any examples of passing Element?
Thanks mark -----Original Message----- From: Chris Haddad [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:14 PM To: [EMAIL PROTECTED] Subject: RE: XML as a Parameter Mark - yes, Axis supports passing 'Element' both from a client and server perspective. The implementation will then not escape the parameter value. How's interop on the MS side with Element? /Chris -----Original Message----- From: Mark Kurley [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 11:12 AM To: '[EMAIL PROTECTED]' Subject: RE: XML as a Parameter Chris Thanks for the help. I was working with this an noticed that it will escape the "xml" because it is a string parameter. When using the NS_URI_LITERAL_XML in Apache-Soap it would add the xml to the soap body. Something like this. <SOAP-ENV:Body> <ns1:processDocument xmls....> <arg1> <XML> This would be an xml document that is not escaped </XML> </arg1> </ns1:processDocument> </SOAP-ENV:Body> The service method on the server side would accept "Element" which would be the xml document. Basically, you could pass any xml document inside of the soap body without it being escaped. I am trying to get this to work with out escaping the data because the client has that requirement. Do you have any other ideas? Does axis support the passing of xml "Element" objects like Apache-SOAP does? Thanks again for the help -mark -----Original Message----- From: Chris Haddad [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 10:15 AM To: [EMAIL PROTECTED] Subject: RE: XML as a Parameter Mark - Yes, an xml document can be passed as a parameter to an RPC style call. You can simple make the parameter a java.lang.String in your service handler method. Deploy the service, and pull the wsdl using ?wsdl or running Java2WSDL. A client stub generated using WSDL2Java then defines this code for the client: javax.xml.rpc.namespace.QName p0QName = new javax.xml.rpc.namespace.QName("", "credentials"); call.addParameter(p0QName, new javax.xml.rpc.namespace.QName("http://schemas.xmlsoap.org/soap/encoding/ ", "string"), javax.xml.rpc.ParameterMode.PARAM_MODE_IN); .... Object resp = call.invoke(new Object[] {credentials}); /Chris -----Original Message----- From: Mark Kurley [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 9:52 AM To: '[EMAIL PROTECTED]' Subject: XML as a Parameter Is it possible to pass an xml document as a parameter for an RPC call in axis. With Apache-SOAP you can pass xml as a parameter using the Constants.NS_URI_LITERAL_XML. I am looking for the equivalent in axis. Thanks for the help in advance. -mark Visit our website at http://www.p21.com/visit The information in this e-mail is confidential and may contain legally privileged information. It is intended solely for the person or entity to which it is addressed. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, action taken, or action omitted to be taken in reliance on it, is prohibited and may be unlawful. If you received this e-mail in error, please contact the sender and delete the material from any computer. Visit our website at http://www.p21.com/visit The information in this e-mail is confidential and may contain legally privileged information. It is intended solely for the person or entity to which it is addressed. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, action taken, or action omitted to be taken in reliance on it, is prohibited and may be unlawful. If you received this e-mail in error, please contact the sender and delete the material from any computer. Visit our website at http://www.p21.com/visit The information in this e-mail is confidential and may contain legally privileged information. It is intended solely for the person or entity to which it is addressed. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, action taken, or action omitted to be taken in reliance on it, is prohibited and may be unlawful. If you received this e-mail in error, please contact the sender and delete the material from any computer.
