On 1/4/07, Heh, Jonathan <[EMAIL PROTECTED]> wrote:
Thanks for the tip, I can work on adding namespaces. However, is the missing namespace what is not allowing me to process the response?
Yes. Your response elements are defined as local elements to the element <ns:processResponse>, but that element does not appear in the message. (<processResponse> is not the same as <ns:processResponse>).
As a little more information, the web service was not created with Axis (it is developed in C++), and does not handle namespaces. It ignores them in requests and does not use them in the responses. For interoperability, this would be something that needs to be addressed, but for now will this lead to a problem with an Axis Java client expecting the response to contain a namespace and thus not being able to parse the message for its contents? Or is there something else going on that I am unable to parse the response?
You cannot ignore namespaces.
Again, you help is appreciated. Thanks. Jon -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 1:39 PM To: [email protected] Subject: Re: Problem accessing response in client code Your response message element (<processResponse>) is not namespace qualified. For better interoperability, I recommend adding elementFormDefault="qualified" to your schema definition (in which case the child elements of <processResponse> must also be namespace qualified.) Anne On 1/3/07, Heh, Jonathan <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > I am using Axis 1.4 to develop a WSDL first web service. In the attached > WSDL I am providing a service that takes an xml file as an attachment. This > service is accepting the file from the client fine, but when I attempt to > access the values from the response, I am getting null values. > > > > I have also attached the request and response messages from the interaction > and the response contains exactly what I am expecting, however the following > is the output I am getting from the attached Java client code: > > error= null > > result= null > > request is null > > > > Is there an error in the WSDL definition somewhere? Any help on why I am > unable to access this response would be greatly appreciated. > > > > > > > Jonathan Heh > > Engineer/Analyst, Northrop Grumman Integrated Systems > > Main: (843) 744-7520 > > Direct: (843) 377-0645 ext 153 > > FAX: (843) 744-7521 > > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
