Re: highway traffic web service example missing namespace declaration
Posted by Alessandro Vernet on URL: https://discuss.orbeon.com/highway-traffic-web-service-example-missing-namespace-declaration-tp33391p33393.html
Hi Adrian,
Some funky things were happening with namespaces because of a bug in
our XInclude code. Erik fixed this just 2 weeks ago. The change went
in before we release 3.5.1. Is this the version you are using? If not,
you might want to try to upgrade. You will find a reference to that
bug in the list of changes for 3.5.1:
Also, is it possible to call your web service with an XForms
submission? From XPL you can use XForms with the Submission processor
(see link below). XForms submission is designed to allow calls to web
services, and if it is possible for you to use an XForms submission, I
would recommend to do so.
>
> Further problems with this.. the attached pipeline uses an XSLT to
> construct a document, which is then wrapped in the <delegation:execute>
> element using XInclude (thus leaving only business logic in the XSLT), then
> passed to the delegation processor.
>
> The resulting document now has *duplicate* namespace declarations, also
> making it badly formed:
>
> <return
> xmlns:delegation="http://orbeon.org/oxf/xml/delegation"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:oxf="http://www.orbeon.com/oxf/processors"
> xmlns:xi="http://www.w3.org/2001/XInclude"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> xmlns:p="http://www.orbeon.com/oxf/pipeline"
> xmlns:p="http://www.orbeon.com/oxf/pipeline"
> xmlns:xi="http://www.w3.org/2001/XInclude"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:oxf="http://www.orbeon.com/oxf/processors"
> xsi:type="xsd:string">No accidents reported.</return>
>
>
> Adrian Baker wrote:
> I've been experimenting with calling a web service from XPL.
>
> However I notice the example of calling the highway traffic web service
> (http://www.orbeon.com/ops/doc/integration-webservices) can
> return a badly formed document, with no namespace prefix declared for the
> "xsi:type" attribute:
> <return .. xsi:type="xsd:string">No accidents reported.</return>
>
> To avoid the problem I can declare the prefix 'xsi' in the XPL pipeline
> invoking the web service, but this seems totally hacky to rely on this
> prefix being delclared like this - eg, if my prefix name doesn't match
> 'xsi', it won't work.
>
> Is this the fault of the web service or Orbeon?
>
> Adrian
>
>
>
>
>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit
> http://www.messagelabs.com/email > ______________________________________________________________________
> ________________________________
>
>
> --
> You receive this message as a subscriber of the [hidden email] > mailing list.
> To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws >
>
>
> --
> You receive this message as a subscriber of the [hidden email] > mailing list.
> To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws >
>
>