Office Research XML response Jim Sweeney 24.01.2006 22:29:07 I'm not sure if this is the appropriate place to pose this question, but it has to do with MS-Word's ability to parse valid XML. I have an issue with the Office Research web service support and its ability to talk to a JAXRPC jwsdp-generated SOAP server. The problem is that the XML registration response from my service is not recognized by MS Word. I use the Google research service as a point of comparison. The Google SOAP Envelope and Body tags start off this way: <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soap:Body> <RegistrationResponse xmlns="urn:Microsoft.Search"> <RegistrationResult> while my Envelope and Body tags start this way: <?xml version="1.0" encoding="UTF-8"?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="urn:Microsoft.Search"> <env:Body> <ns0:RegistrationResponse> <ns0:RegistrationResult> I've narrowed the problem down to the ns0 namespace alias on the RegistrationResponse and RegistrationResult tags. Although it is a valid XML construct, MS-Word does not like that these names are prefixed with the alias. I'm wondering if Office is going to support this sort of namespace usage soon, or if this represents a hole in Microsoft's XML interoperability. Are there specific Microsoft technical forums that might be able to better address my question or even suggest a work-around? Thanks!

Re: Office Research XML response "willib" <willib[ at ]<|>sqtm.net> 25.01.2006 07:37:42 I think your namespaces are not correct. a cutout from mysample <?xml version="1.0" encoding="utf-8"?> <ResponsePacket revision="1" xmlns="urn:Microsoft.Search.Response"> <Response domain="{.. research guid here..}"> <Range> <StartAt>1</StartAt> <Count>5</Count> <TotalAvailable>0</TotalAvailable> <Results> <Content xmlns="urn:Microsoft.Search.Response.Content"> ....rest of the packet hth willib "Jim Sweeney" <Jim Sweeney[ at ]discussions.microsoft.com> wrote in message news:9757AA57-A022-45D6-843B-2320783B3C62[ at ]microsoft.com... [Quoted Text] > I'm not sure if this is the appropriate place to pose this question, but it > has to do with MS-Word's ability to parse valid XML. I have an issue with > the Office Research web service support and its ability to talk to a JAXRPC > jwsdp-generated SOAP server. > > The problem is that the XML registration response from my service is not > recognized by MS Word. I use the Google research service as a point of > comparison. > > The Google SOAP Envelope and Body tags start off this way: > > <?xml version="1.0" encoding="utf-8"?> > <soap:Envelope > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <soap:Body> > <RegistrationResponse xmlns="urn:Microsoft.Search"> > <RegistrationResult> > > while my Envelope and Body tags start this way: > > <?xml version="1.0" encoding="UTF-8"?> > <env:Envelope > xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" > xmlns:ns0="urn:Microsoft.Search"> > <env:Body> > <ns0:RegistrationResponse> > <ns0:RegistrationResult> > > I've narrowed the problem down to the ns0 namespace alias on the > RegistrationResponse and RegistrationResult tags. Although it is a valid XML > construct, MS-Word does not like that these names are prefixed with the > alias. I'm wondering if Office is going to support this sort of namespace > usage soon, or if this represents a hole in Microsoft's XML interoperability. > > Are there specific Microsoft technical forums that might be able to better > address my question or even suggest a work-around? > > Thanks! >

Re: Office Research XML response Jim Sweeney 25.01.2006 17:31:04 Your sample is of a Search Response. The snippets I posted above are both for a Registration Response. The first one is for the Google service which works and the 2nd is for my service which doesn't work. The only difference is that an alias is used to refer to the namespace. This is perfectly valid XML and I'm just wondering why MS-Word can't parse it. Jim "willib sqtm.net>" wrote: [Quoted Text] > > I think your namespaces are not correct. > a cutout from mysample > > <?xml version="1.0" encoding="utf-8"?> > <ResponsePacket revision="1" xmlns="urn:Microsoft.Search.Response"> > <Response domain="{.. research guid here..}"> > <Range> > <StartAt>1</StartAt> > <Count>5</Count> > <TotalAvailable>0</TotalAvailable> > <Results> > <Content xmlns="urn:Microsoft.Search.Response.Content"> > ....rest of the packet

Re: Office Research XML response "willib" <willib[ at ]<|>sqtm.net> 25.01.2006 18:27:32 hello i have not try'd to namespace prefix my sample but your namespace xmlns:ns0="urn:Microsoft.Search" is different to: <?xml version="1.0" encoding="utf-8"?> <ProviderUpdate xmlns="urn:Microsoft.Search.Registration.Response"> <Status>SUCCESS</Status> <Providers> <Provider> <Message> Beschreibung der Funktionalität des Webdienst.</Message> <Id>{ guid }</Id> <Name>myWebdienst</Name> <QueryPath/> <RegistrationPath/> <AboutPath/> <Type>SOAP</Type> <Services> <Service> <Id>{service_guid}</Id> <Name> Suche </Name> <Description> Webdienst .</Description> <Copyright>2004 by willib</Copyright> <Display>On</Display> <Category>RESEARCH_GENERAL</Category> </Service> </Services> </Provider> </Providers> </ProviderUpdate> While the development i run into trubble using the right quid's and id's.for the services. hth wilib "Jim Sweeney" <JimSweeney[ at ]discussions.microsoft.com> wrote in message news:85BA729D-5971-4280-9530-7ADCD6E2FF59[ at ]microsoft.com... [Quoted Text] > Your sample is of a Search Response. The snippets I posted above are both > for a Registration Response. The first one is for the Google service which > works and the 2nd is for my service which doesn't work. The only difference > is that an alias is used to refer to the namespace. This is perfectly valid > XML and I'm just wondering why MS-Word can't parse it. > > Jim > > "willib sqtm.net>" wrote: > > > > > I think your namespaces are not correct. > > a cutout from mysample > > > > <?xml version="1.0" encoding="utf-8"?> > > <ResponsePacket revision="1" xmlns="urn:Microsoft.Search.Response"> > > <Response domain="{.. research guid here..}"> > > <Range> > > <StartAt>1</StartAt> > > <Count>5</Count> > > <TotalAvailable>0</TotalAvailable> > > <Results> > > <Content xmlns="urn:Microsoft.Search.Response.Content"> > > ....rest of the packet >

Re: Office Research XML response Jim Sweeney 25.01.2006 19:00:01 Yes, as I explained, your sample is a Search response. My sample is a *Registration* response, so you're comparing two different things. Jim "willib sqtm.net>" wrote: [Quoted Text] > hello > > i have not try'd to namespace prefix my sample > but your namespace xmlns:ns0="urn:Microsoft.Search" > is different to: > > <?xml version="1.0" encoding="utf-8"?> > <ProviderUpdate xmlns="urn:Microsoft.Search.Registration.Response"> > <Status>SUCCESS</Status>