No, I don't, at least partly because the "literal XML" encoding used in that example is specific to Apache SOAP and not intended for general interoperability.
On 29 May 2003 at 14:29, Vishal Shah wrote: > Scott, > > Do you happen to have a VB 6 code snippet that calles "getAllListings()" method of > AddressBook sample (urn:AddressFetcher). This method returns a DOM element...and > wanted to extrapolate... > > Thanks, > > Scott Nichol <[EMAIL PROTECTED]> wrote: > Doesn't your service have to use "literal XML encoding" to return an > Element? This is specific to Apache SOAP. It is not a standard > encoding. I am not sure what other implementations might support it, > but Microsoft does not. > > On 22 May 2003 at 9:20, Vishal Shah wrote: > > > Hi, > > > > I've been getting a following error when a VB6 client using SOAP high-level API, > > is trying to call a service that returns a DOM element. > > > > "No Serializer found to serialize a 'org.w3c.dom.Element' using encoding style..." > > > > I've been scouring through for a possible fix. Pl let me know... > > > > Thanks > > VS > > > > > > --------------------------------- > > Do you Yahoo!? > > The New Yahoo! Search - Faster. Easier. Bingo. > > > Scott Nichol > > Do not reply directly to this e-mail address, > as it is filtered to only receive e-mail from > specific mailing lists. > > > > --------------------------------- > Do you Yahoo!? > Free online calendar with sync to Outlook(TM). Scott Nichol Do not reply directly to this e-mail address, as it is filtered to only receive e-mail from specific mailing lists.
