highway traffic web service example missing namespace declaration

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








--
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

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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

<?xml version="1.0"?>
<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
                xmlns:oxf="http://www.orbeon.com/oxf/processors"
                xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:xi="http://www.w3.org/2001/XInclude"
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       
        <p:param type="output" name="clinical-document" />
        <p:param type="input" name="parameters"/>
       
        <p:processor name="oxf:xslt">
                <p:input name="data" href="#parameters"/>
                <p:input name="config">
                        <hwynums xsl:version="2.0">
                                <xsl:value-of select="/parameters/highway"/>
                        </hwynums>
                </p:input>
                <p:output name="data" id="xslt-result"/>
        </p:processor>
       
        <p:processor name="oxf:xinclude">
                <p:input name="config">
                        <delegation:execute service="ca-traffic" operation="getTraffic" xmlns:delegation="http://orbeon.org/oxf/xml/delegation" xmlns="">
                                <xi:include href="input:xslt-result"/>
                        </delegation:execute>
                </p:input>
                <p:input name="xslt-result" href="#xslt-result"/>
                <p:output name="data" id="web-service-call"/>
        </p:processor>
       
        <p:processor name="oxf:delegation">
                <p:input name="interface">
                        <config>
                                <service id="ca-traffic" type="webservice" endpoint="http://services.xmethods.net/soap/servlet/rpcrouter">
                                        <operation nsuri="urn:xmethods-CATraffic" name="getTraffic"/>
                                </service>
                        </config>
                </p:input>
                <p:input name="call" debug="true" href="#web-service-call"/>
                <p:output name="data" ref="clinical-document" debug="true"/>
        </p:processor>

</p:config>



--
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

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:

http://www.orbeon.com/ops/doc/home-changes-35

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.

http://www.orbeon.com/ops/doc/processors-submission

Alex

On 4/10/07, Adrian Baker <[hidden email]> wrote:
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
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

Hi Alex,

Alessandro Vernet wrote:

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:

http://www.orbeon.com/ops/doc/home-changes-35

I'm using a version of 3.5 milestone 1, so at some stage I'll try the later version - thanks.

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.

http://www.orbeon.com/ops/doc/processors-submission

The XPL pipeline isn't being invoked from XForms: in this case we're just using XPL as an integration tool within the back end of the application.

Adrian

--
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

Hi Adrian,

On 4/11/07, Adrian Baker <[hidden email]> wrote:
>  I'm using a version of 3.5 milestone 1, so at some stage I'll try the later
> version - thanks.

OK, you'll let us know how this works.

>  The XPL pipeline isn't being invoked from XForms: in this case we're just
> using XPL as an integration tool within the back end of the application.

That is fine: the XForms submission processor is designed so you can
use just the XForms submission part of XForms on the back-end from
XPL.

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
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

Alessandro Vernet wrote:
>> using XPL as an integration tool within the back end of the application.
>  The XPL pipeline isn't being invoked from XForms: in this case we're
> just
>
> That is fine: the XForms submission processor is designed so you can
> use just the XForms submission part of XForms on the back-end from
> XPL.
>
> Alex

Right, sorry now I understand - the XForms submission XPL processor can
be used in a pipeline, even if XForms are not involved? I'll keep this
in mind.

Adrian




--
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

On 4/11/07, Adrian Baker <[hidden email]> wrote:
> Right, sorry now I understand - the XForms submission XPL processor can
> be used in a pipeline, even if XForms are not involved? I'll keep this
> in mind.

Exactly. Right now this is just to run an XForms submission, but we
are working on enhancing this so you can use all the power of XForms
in the back-end.

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
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