> Hello Alex,
>
> That could be the case... never thought of that. While submitting I use "replace=instance"; my guess would be that this does not submit the xforms:bind as well..?
>
> Best, Robin
>
> -----Oorspronkelijk bericht-----
> Van: Alessandro Vernet [mailto:[hidden email]]
> Verzonden: woensdag 24 februari 2010 0:57
> Aan: [hidden email]
> Onderwerp: [ops-users] Re: RE: Re: Strange behaviour on Orbeon 3.7.1
>
> Robin,
>
> Could this be due to the fact that non-relevant nodes (set as such
> with xforms:bind) are not sent when running an xforms:submission?
>
> Alex
>
> On Mon, Feb 22, 2010 at 6:20 AM, Robin Diederen <[hidden email]> wrote:
>> Hello Alex,
>>
>> Except for the data / values the documents are 100% identical. The Xforms
>> inspector confirms this.
>>
>>
>>
>> Meanwhile I've found where the problem originates: using the document
>> returend in an xforms:bind results in this behaviour. I really don't
>> understand why, I just know it does. For now I've built a workaround (I've
>> eliminated the xforms:bind) and all works fine. This doesn't explain this
>> behaviour though.
>>
>>
>>
>> Best, Robin
>>
>> -----Original message-----
>> From: Alessandro Vernet <[hidden email]>
>> Sent: Sat 20-02-2010 00:42
>> To: [hidden email];
>> Subject: [ops-users] Re: Strange behaviour on Orbeon 3.7.1
>>
>> Robin,
>>
>> I don't see why it would work in one case, but not in the other. There
>> must be a difference, other than in the value returned (1 vs. 622).
>> Have you tried using the XForms inspector to look at the instances? Is
>> the XML exactly the same in both cases (including the namespace
>> declarations)?
>>
>> Alex
>>
>> On Fri, Feb 19, 2010 at 3:28 AM, Robin Diederen <[hidden email]> wrote:
>>> Hello all,
>>>
>>>
>>>
>>> I'm building an application on Orbeon 3.7.1. I've built a pipeline which
>>> performs a SOAP call. The outcome of that call is used on my form. At
>>> least,
>>> most of the times it is (and that's exactly my problem).
>>>
>>>
>>>
>>> For instance:
>>>
>>>
>>>
>>> I perform a SOAP call. A part of the document returned is:
>>>
>>>
>>> "<rsp:paginateResult><rsp:page>1</rsp:page><rsp:totalPages>63</rsp:totalPages><rsp:totalResults>622</rsp:totalResults></rsp:paginateResult>"
>>>
>>>
>>>
>>> When I want to print a value, totalResults for example, using a construct
>>> like "<xforms:output
>>> ref="instance('query-response')//rsp:totalResults"/>",
>>> I get exactly the result to be expected: 622
>>>
>>>
>>>
>>> However... when I get another search result (now the documented returned
>>> looks
>>>
>>> like "<rsp:paginateResult><rsp:page>1</rsp:page><rsp:totalPages>1</rsp:totalPages><rsp:totalResults>1</rsp:totalResults></rsp:paginateResult>")
>>> and I print again using the same xforms:output, nothing is printed at all.
>>>
>>>
>>>
>>> Would anybody have a clue how and why this can happen? I have checked the
>>> returned documents from the SOAP call and they are all just fine.
>>>
>>>
>>>
>>> Best, Robin
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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
>>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>>
>>>
>>
>>
>>
>> --
>> Orbeon Forms - Web forms, open-source, for the Enterprise -
>> http://www.orbeon.com/
>> My Twitter: http://twitter.com/avernet
>>
>>
>> --
>> 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
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>>
>
>
>
> --
> Orbeon Forms - Web forms, open-source, for the Enterprise -
> http://www.orbeon.com/
> My Twitter: http://twitter.com/avernet
>
>
>
> --
> 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
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>