FW: Client and Server side samples for testing the XSD:ANY - has Changed due to the modifications done to AxisException

[Amila Rathnayake <wr...@yahoo.com>]

       Clean  Clean  DocumentEmail                    MicrosoftInternetExplorer4 st1\:*{behavior:url(#default#ieooui) } /* Style Definitions */  table.MsoNormalTable	{mso-style-name:"Table Normal";	mso-tstyle-rowband-size:0;	mso-tstyle-colband-size:0;	mso-style-noshow:yes;	mso-style-parent:"";	mso-padding-alt:0in 5.4pt 0in 5.4pt;	mso-para-margin:0in;	mso-para-margin-bottom:.0001pt;	mso-pagination:widow-orphan;	font-size:10.0pt;	font-family:"Times New Roman";}
Hi All,

 

In the CVS AxisException.cpphas changed to AxisGenException.cpp. Due to thisreason the sampleClent that I have sent earlier shouldbe changed a bit.

 

In all the catch blocks the exceptionshould be changed from AxisException to AxisGenException.

 

Here I have attached the modified file inthe client side.

 

You can replace the existing ExtensibilityQueryPortType.cpp in the sampleClientwith this file.

 

 

BTW thank you Susanthafor adding required functions in the parser to get the namespace prefix forgiven uri.

Right now, it#8217;s avilablein the wrapper of EXPAT parser. So I will start testing with that. Once youfinish adding that to Xerces wrapper I will test thatas well.

 

Thanks and Regards,

Amila Rathnayake.

 

 

 

-----Original Message-----
From: Amila Rathnayake[mailto:writetoamila@yahoo.com] 
Sent: Wednesday, June 23, 2004 6:15 PM
To: axis-c-dev@ws.apache.org
Subject: Client and Server sidesamples for testing the XSD:ANY

 

Hi All,

 

Here, I am sending the sample application to test thexsd:any type support. Please find the sampleClient, sampleServer and therelevant WSDL file with the attachments.

 

In this sample it has used the wsdl file calledExtensibilityQuery.wsdl to generate the server side skeletons and client stubs.In this wsdl it has used xsd:any type.

 

>From the client side I have passed a sample XML string andsee whether it has added that xml string properly in to the returned array inthe anyType, after serialization and deserialization.

 

 

There is still the issue that I have sent earlier. When itDeSeralize the xml string it#8217;s adding the namespace uri instead ofnamespace prefix. This is because there is no such method to return the prefixfor given namespace in the parser.

 

Adding this method will lead to another change of the parserAPI, but to deseralize the xsd:any type properly we need to have that method inthe parser wrappers.

 

I have tested this sample and also the request and responseSOAP messages and they are in the correct form except the above mentionedprefix problem. So that the response SOAP message is not in the correct form toview in the browser. We can keep this sample until we add that functionalityinto the parser. Once we have added this, I can change the SoapDeSerializer toinclude the correct prefix in the response.

 

Thanks and Regards,

Amila Rathnayake.

 

 


		
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
		
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!