No. Why cant we loop around the m_pNode's, peek into their m_pchNameOrValue and deserialize based on that? No need for a pull here. This is plain vanilla xml stuff, you will not see any guidance in the web services standards. This is supposed to work :)
-- dims On Mon, 21 Mar 2005 10:41:41 +0000, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > > > The current code generation tool is dependent on the WSDL alone to > determine the ordering of the elements. > As the parser uses pull model, the engine is not capable as of not to > deal with the order changes. It will take *lot* of effort to change this > pull model - it is the very reason why href/multiref is also not > supported. > > Yes we assume the order to be the same as in WSDL - have to see what > WS-I and other interop guides say in relation to this assumption. If > interop guides do allow for change in order, we may have to do some > *major* changes to XML parsing in the engine. > > Thanks, > Samisa... > > > On Mon, 2005-03-21 at 04:17, Davanum Srinivas wrote: > > Samisa, Team, > > > > Looks like the current code is *BAD* at handling cases where the > > ordering of the elements on the wire is different from that specified > > in wsdl/xsd....See enclosed diff that i had to apply to the generated > > code to make it work. If people can't use public web services with our > > code...they will have a hard time justifying its usage. > > > > Thanks, > > dims > > > > > > On Mon, 21 Mar 2005 07:55:48 +0000, Samisa Abeysinghe > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > Sorry, I did not get any time to look into this these days. > > > > > > Thanks, > > > Samisa... > > > > > > On Sat, 2005-03-19 at 13:37, Davanum Srinivas wrote: > > > > Samisa, > > > > > > > > Any word on this? > > > > > > > > thanks, > > > > dims > > > > > > > > > > > > On Wed, 9 Mar 2005 10:01:54 +0600, Samisa Abeysinghe > > > > <[EMAIL PROTECTED]> wrote: > > > > > Hi Krishna, > > > > > As there are quite a number of files that I would have to look > > > > > into, please give me some time. > > > > > I will get back to you. > > > > > Thanks, > > > > > Samisa... > > > > > > > > > > -----Original Message----- > > > > > From: krishna [mailto:[EMAIL PROTECTED] > > > > > Sent: Wednesday, March 09, 2005 7:05 AM > > > > > To: [email protected] > > > > > Cc: Krishna Kumar Rajagopalan > > > > > Subject: Re:Google with Axis > > > > > > > > > > Hi Samisa > > > > > > > > > > I have attached the source code files with a description. > > > > > > > > > > 1.Google.cpp - File written by me for Client side which calls > > > > > doGoogleSearch > > > > > > > > > > 2.GoogleSearchPort.cpp1(renamed) - Original GoogleSearchPort .cpp file > > > > > generated by wsdl2ws tool > > > > > > > > > > 3.error1 - SOAP message generated when GoogleSearchPort.cpp1 was > > > > > used > > > > > > > > > > 4.GoogleSearchPort2.cpp2(modified) - Order of function calls changed > > > > > to > > > > > that of wsdl as shown below > > > > > > > > > > m_pCall->addParameter((void*)&Value1, "key", > > > > > XSD_STRING); > > > > > m_pCall->addParameter((void*)&Value9, "q", > > > > > XSD_STRING); > > > > > m_pCall->addParameter((void*)&Value3, "start", > > > > > XSD_INT); > > > > > m_pCall->addParameter((void*)&Value7, "maxResults", > > > > > XSD_INT); > > > > > m_pCall->addParameter((void*)&Value0, "filter", > > > > > XSD_BOOLEAN); > > > > > m_pCall->addParameter((void*)&Value2, "restrict", > > > > > XSD_STRING); > > > > > m_pCall->addParameter((void*)&Value5, "safeSearch", > > > > > XSD_BOOLEAN); > > > > > m_pCall->addParameter((void*)&Value6, "lr", > > > > > XSD_STRING); > > > > > m_pCall->addParameter((void*)&Value4, "ie", > > > > > XSD_STRING); > > > > > m_pCall->addParameter((void*)&Value8, "oe", > > > > > XSD_STRING); > > > > > > > > > > 5.error2 - SOAP message generated when GoogleSearchPort.cpp2(modified) > > > > > was used > > > > > > > > > > 6.All other files generated by the WSDL2WS tool are attached > > > > > > > > > > 7.compile - sample script to compile files > > > > > > > > > > After the run with GoogleSearchPort.cpp2(modified) the code exits > > > > > with a > > > > > > > > > > segmentation fault > > > > > > > > > > Regards > > > > > Krishna > > > > > > > > > > uic.edu/~krajag2 > > > > > > > > > > Hi Krishna, > > > > > It would be helpfult to fix this problem if you could send the > > > > > SOAP message and the generated code that you are using. > > > > > > > > > > Thanks, > > > > > Samisa,,, > > > > > > > > > > > > > -- > > > Samisa Abeysinghe <[EMAIL PROTECTED]> > > > Virtusa Corporation > > > > > > --------------------------- > > > ----------------------------------------------------------------- > > > This message, including any attachments, contains confidential > > > information intended for a specific individual and purpose, and is > > > intended for the addressee only. Any unauthorized disclosure, use, > > > dissemination, copying, or distribution of this message or any of its > > > attachments or the information contained in this e-mail, or the taking of > > > any action based on it, is strictly prohibited. If you are not the > > > intended recipient, please notify the sender immediately by return e-mail > > > and delete this message. > > > > > > --------------------------------------------------------------------------------------------- > > > This message, including any attachments, contains confidential > > > information intended for a specific individual and purpose, and is > > > intended for the addressee only. Any unauthorized disclosure, use, > > > dissemination, copying, or distribution of this message or any of its > > > attachments or the information contained in this e-mail, or the taking of > > > any action based on it, is strictly prohibited. If you are not the > > > intended recipient, please notify the sender immediately by return e-mail > > > and delete this message. > > > > -- > Samisa Abeysinghe <[EMAIL PROTECTED]> > Virtusa Corporation > > --------------------------- > ----------------------------------------------------------------- > This message, including any attachments, contains confidential information > intended for a specific individual and purpose, and is intended for the > addressee only. Any unauthorized disclosure, use, dissemination, copying, or > distribution of this message or any of its attachments or the information > contained in this e-mail, or the taking of any action based on it, is > strictly prohibited. If you are not the intended recipient, please notify the > sender immediately by return e-mail and delete this message. > > --------------------------------------------------------------------------------------------- > This message, including any attachments, contains confidential information > intended for a specific individual and purpose, and is intended for the > addressee only. Any unauthorized disclosure, use, dissemination, copying, or > distribution of this message or any of its attachments or the information > contained in this e-mail, or the taking of any action based on it, is > strictly prohibited. If you are not the intended recipient, please notify the > sender immediately by return e-mail and delete this message. > -- Davanum Srinivas - http://webservices.apache.org/~dims/
