RE: Handmade WSDL?
Don't waste the effort! Instead, fix it at the source. . . -Original Message- From: Airline Pedestal [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 01, 2005 6:29 PM To: axis-user@ws.apache.org; Anne Thomas Manes Subject: Re: Handmade WSDL? Hi Anne, Could you provide an example how to extract that? Thanks, A --- Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > Ah -- I see. This DataSet is coming from a .NET service (probably > generated by ADO.NET), and then stuffed into the SOAP message as a > string. Unfortunately, because the string starts with the > declaration, you won't be able to get Axis to process it for you. You > are going to have to extract the string and then process it using SAX > or DOM. > > You need to go abuse the card processing folks. This is what's known > as a "worst practice". > > Anne > __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail
Re: Handmade WSDL?
Hi Anne, Could you provide an example how to extract that? Thanks, A --- Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > Ah -- I see. This DataSet is coming from a .NET > service (probably > generated by ADO.NET), and then stuffed into the > SOAP message as a > string. Unfortunately, because the string starts > with the > declaration, you won't be able to get Axis to > process it for you. You > are going to have to extract the string and then > process it using SAX > or DOM. > > You need to go abuse the card processing folks. This > is what's known > as a "worst practice". > > Anne > __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail
Re: Handmade WSDL?
Thank you so very much. I suspected something like this, especially after investigating a well-formed SOAP service (from Melissa Data) and working through the client code generated by WSDL2Java for it. I'm pretty new to all of this so I have to keep looking up everything. And it seems that everything I'm learning involves twelve other things to learn as well. ;) Gotta love it . . . Elaine Anne Thomas Manes wrote: Ah -- I see. This DataSet is coming from a .NET service (probably generated by ADO.NET), and then stuffed into the SOAP message as a string. Unfortunately, because the string starts with the declaration, you won't be able to get Axis to process it for you. You are going to have to extract the string and then process it using SAX or DOM. You need to go abuse the card processing folks. This is what's known as a "worst practice". Anne <~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~
Re: Handmade WSDL?
Ah -- I see. This DataSet is coming from a .NET service (probably generated by ADO.NET), and then stuffed into the SOAP message as a string. Unfortunately, because the string starts with the declaration, you won't be able to get Axis to process it for you. You are going to have to extract the string and then process it using SAX or DOM. You need to go abuse the card processing folks. This is what's known as a "worst practice". Anne
Re: Handmade WSDL?
Thanks for the input, I truly, truly appreciate the help. I am working on setting up the client as an Axis app so I can use the tcpmon and capture the SOAP streams. (So far I've pretty much been using the command-line.) When I get it up I'll post the message with SOAP headers and all. ITMT, here is the returned String: http://www.w3.org/2001/XMLSchema"; xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> data:IsDataSet="true";> 5 Edit-error - AVS data is invalid 6 E Thanks again, Elaine Anne Thomas Manes wrote: Actually, I just realized that there might be one more layer of wrapper in the response message. If you can give a sample SOAP response message, that would help. But, based on your current WSDL definition, I expect your response message schema to look like this: On Mon, 28 Feb 2005 18:28:36 -0500, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: I'm with Dino. I think you should convince your card processing service people to provide you with a decent schema. My chief concern is in regards to future maintenance. What if these "card processing service" people decide to change the message structure at some point in the future. Do they have a plan to inform you of these changes? If they aren't willing to provide you with a schema, then it's relatively easy for you to construct one from the format they've supplied. Do you know if they are using any namespaces in the XML string? Your sample shows no namespaces, but if they add them, that will definitely impact your WSDL definition. Your schema should look like this: - Anne On Mon, 28 Feb 2005 14:43:23 -0800, Dino Chiesa <[EMAIL PROTECTED]> wrote: Not stupid... Your approach is reasonable, but... Can you not contact the "card processing service" people and ask them to resolve the difference between the doc and the WSDL ? -Original Message- From: Elaine Nance [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 3:45 PM To: axis-user@ws.apache.org Subject: Handmade WSDL? Hope this is not stupid, but Problem: the wsdl for our (supposedly) enterprise credit card processing service shows well defined request parameters, but the SOAP responses are all designated as string, as shown below. I am thinking that the best way to generate the client stubs I need in Java is to create a wsdl with better response typing and generate the stubs using WSDL2Java and then test. Does it make sense to proceed like the above? or should I just build parsers using SAX or DOM or whatever? Thank you, Elaine - example request - example response as given - WHAT THE RESPONSE SHOULD LOOK LIKE (I THINK) - ALTERNATIVELY - the web service docs indicate that the xml returned (minus SOAP envelope) will look like the following: 1 No Address Supplied 1 E <~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~
Re: Handmade WSDL?
Actually, I just realized that there might be one more layer of wrapper in the response message. If you can give a sample SOAP response message, that would help. But, based on your current WSDL definition, I expect your response message schema to look like this: On Mon, 28 Feb 2005 18:28:36 -0500, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > I'm with Dino. I think you should convince your card processing > service people to provide you with a decent schema. My chief concern > is in regards to future maintenance. What if these "card processing > service" people decide to change the message structure at some point > in the future. Do they have a plan to inform you of these changes? > > If they aren't willing to provide you with a schema, then it's > relatively easy for you to construct one from the format they've > supplied. Do you know if they are using any namespaces in the XML > string? Your sample shows no namespaces, but if they add them, that > will definitely impact your WSDL definition. > > Your schema should look like this: > > > > > > > > > > > name="AVSCode" type="s:string"/> > name="AVSMessage" type="s:string"/> > name="ID" type="s:string"/> > name="Status" type="s:string"/> > > > > > > > > > > > - Anne > > > On Mon, 28 Feb 2005 14:43:23 -0800, Dino Chiesa <[EMAIL PROTECTED]> wrote: > > Not stupid... > > > > Your approach is reasonable, but... Can you not contact the "card > > processing service" people and ask them to resolve the difference > > between the doc and the WSDL ? > > > > > > -Original Message- > > From: Elaine Nance [mailto:[EMAIL PROTECTED] > > Sent: Monday, February 28, 2005 3:45 PM > > To: axis-user@ws.apache.org > > Subject: Handmade WSDL? > > > > Hope this is not stupid, but > > > > Problem: the wsdl for our (supposedly) enterprise credit card > > processing service shows well defined request parameters, but the > > SOAP responses are all designated as string, as shown below. > > > > I am thinking that the best way to generate the client stubs I need in > > Java is to create a wsdl with better response typing and generate the > > stubs using WSDL2Java and then test. > > > > Does it make sense to proceed like the above? or should I just build > > parsers using SAX or DOM or whatever? > > > > Thank you, > > Elaine > > > > - example request > > > > > > > > > type="s:string" /> > > > > > > > > > > - example response as given > > > > > > > > > name="GetAVSResponseCodeValueResult" type="s:string" /> > > > > > > > > > > - WHAT THE RESPONSE SHOULD LOOK LIKE (I THINK) > name="GetAVSResponseCodeValueResponse"> > > > > > > > type="s:string"/> > > > type="s:string"/> > > > type="s:string"/> > > > type="s:string"/> > > > > > > > > > > - ALTERNATIVELY > > > > > > > > > type="s:string"/> > > > type="s:string"/> > > > type="s:string"/> > > > type="s:string"/> > > > > > > > > > > - the web service docs indicate that the xml returned (minus SOAP > > envelope) will look like the following: > > > > > > > > 1 > > No Address Supplied > > 1 > > E > > > > > > > > <~~ > > | Computers are useless. They can only give you answers. > > | -- Pablo Picasso -- > > <~~ > > > > >
Re: Handmade WSDL?
I'm with Dino. I think you should convince your card processing service people to provide you with a decent schema. My chief concern is in regards to future maintenance. What if these "card processing service" people decide to change the message structure at some point in the future. Do they have a plan to inform you of these changes? If they aren't willing to provide you with a schema, then it's relatively easy for you to construct one from the format they've supplied. Do you know if they are using any namespaces in the XML string? Your sample shows no namespaces, but if they add them, that will definitely impact your WSDL definition. Your schema should look like this: - Anne On Mon, 28 Feb 2005 14:43:23 -0800, Dino Chiesa <[EMAIL PROTECTED]> wrote: > Not stupid... > > Your approach is reasonable, but... Can you not contact the "card > processing service" people and ask them to resolve the difference > between the doc and the WSDL ? > > > -Original Message- > From: Elaine Nance [mailto:[EMAIL PROTECTED] > Sent: Monday, February 28, 2005 3:45 PM > To: axis-user@ws.apache.org > Subject: Handmade WSDL? > > Hope this is not stupid, but > > Problem: the wsdl for our (supposedly) enterprise credit card > processing service shows well defined request parameters, but the > SOAP responses are all designated as string, as shown below. > > I am thinking that the best way to generate the client stubs I need in > Java is to create a wsdl with better response typing and generate the > stubs using WSDL2Java and then test. > > Does it make sense to proceed like the above? or should I just build > parsers using SAX or DOM or whatever? > > Thank you, > Elaine > > - example request > > > > type="s:string" /> > > > > > - example response as given > > > > name="GetAVSResponseCodeValueResult" type="s:string" /> > > > > > - WHAT THE RESPONSE SHOULD LOOK LIKE (I THINK) name="GetAVSResponseCodeValueResponse"> > > > type="s:string"/> > type="s:string"/> > type="s:string"/> > type="s:string"/> > > > > > - ALTERNATIVELY > > > > type="s:string"/> > type="s:string"/> > type="s:string"/> > type="s:string"/> > > > > > - the web service docs indicate that the xml returned (minus SOAP > envelope) will look like the following: > > > > 1 > No Address Supplied > 1 > E > > > > <~~ > | Computers are useless. They can only give you answers. > | -- Pablo Picasso -- > <~~ > >
Re: Handmade WSDL?
Well, I can contact the project manager and ask, but that would be effective only if I rewrite the WSDL first and include samples. The project manager is not a programmer. ITMT, which form of the changed WSDL below will be best? The responses which return xml documents (as strings) all seem to use the root element of , which I think violates the WSDL specification for uniqueness. [?] I am currently reading the WSDL 1.1 W3C Note dated 15 March 2001, but the published wsdl doesn't seem to quite match with that, and this doc is definitely *not* WSDL 2.0 compliant. Really appreciate the input. :) I want to do this as well as possible. Thanks again, Elaine Dino Chiesa wrote: Not stupid... Your approach is reasonable, but... Can you not contact the "card processing service" people and ask them to resolve the difference between the doc and the WSDL ? -Original Message- From: Elaine Nance [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 3:45 PM To: axis-user@ws.apache.org Subject: Handmade WSDL? Hope this is not stupid, but Problem: the wsdl for our (supposedly) enterprise credit card processing service shows well defined request parameters, but the SOAP responses are all designated as string, as shown below. I am thinking that the best way to generate the client stubs I need in Java is to create a wsdl with better response typing and generate the stubs using WSDL2Java and then test. Does it make sense to proceed like the above? or should I just build parsers using SAX or DOM or whatever? Thank you, Elaine - example request - example response as given - WHAT THE RESPONSE SHOULD LOOK LIKE (I THINK) name="GetAVSResponseCodeValueResponse"> - ALTERNATIVELY - the web service docs indicate that the xml returned (minus SOAP envelope) will look like the following: 1 No Address Supplied 1 E <~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~
RE: Handmade WSDL?
Not stupid... Your approach is reasonable, but... Can you not contact the "card processing service" people and ask them to resolve the difference between the doc and the WSDL ? -Original Message- From: Elaine Nance [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 3:45 PM To: axis-user@ws.apache.org Subject: Handmade WSDL? Hope this is not stupid, but Problem: the wsdl for our (supposedly) enterprise credit card processing service shows well defined request parameters, but the SOAP responses are all designated as string, as shown below. I am thinking that the best way to generate the client stubs I need in Java is to create a wsdl with better response typing and generate the stubs using WSDL2Java and then test. Does it make sense to proceed like the above? or should I just build parsers using SAX or DOM or whatever? Thank you, Elaine - example request - example response as given - WHAT THE RESPONSE SHOULD LOOK LIKE (I THINK) - ALTERNATIVELY - the web service docs indicate that the xml returned (minus SOAP envelope) will look like the following: 1 No Address Supplied 1 E <~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~
Handmade WSDL?
Hope this is not stupid, but Problem: the wsdl for our (supposedly) enterprise credit card processing service shows well defined request parameters, but the SOAP responses are all designated as string, as shown below. I am thinking that the best way to generate the client stubs I need in Java is to create a wsdl with better response typing and generate the stubs using WSDL2Java and then test. Does it make sense to proceed like the above? or should I just build parsers using SAX or DOM or whatever? Thank you, Elaine - example request - example response as given - WHAT THE RESPONSE SHOULD LOOK LIKE (I THINK) - ALTERNATIVELY - the web service docs indicate that the xml returned (minus SOAP envelope) will look like the following: 1 No Address Supplied 1 E <~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~
