Strange behaviour on Orbeon 3.7.1
Locked
Strange behaviour on Orbeon 3.7.1
 
|
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 |
Re: Strange behaviour on Orbeon 3.7.1
Administrator
|
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
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
RE: Re: Strange behaviour on Orbeon 3.7.1
|
|
Hello Alex,
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----- -- 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 |
Re: RE: Re: Strange behaviour on Orbeon 3.7.1
|
Administrator
|
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
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
RE: Re: RE: Re: Strange behaviour on Orbeon 3.7.1
|
|
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 |
Re: RE: Re: RE: Re: Strange behaviour on Orbeon 3.7.1
|
Administrator
|
Robin,
A submission always submits instance content, not XForms constructs (such as binds or models or controls). -Erik On Wed, Feb 24, 2010 at 2:06 PM, Robin Diederen <[hidden email]> wrote: > 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 > > -- 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 |
Re: Re: RE: Re: RE: Re: Strange behaviour on Orbeon 3.7.1
|
Administrator
|
Robin,
To clarify, like Erik said, your instance will be submitted, and in the instance the non-relevant nodes will be pruned. Alex On Wed, Feb 24, 2010 at 8:17 AM, Erik Bruchez <[hidden email]> wrote: > Robin, > > A submission always submits instance content, not XForms constructs > (such as binds or models or controls). > > -Erik > > On Wed, Feb 24, 2010 at 2:06 PM, Robin Diederen <[hidden email]> wrote: >> 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 >> >> > > > -- > 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
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Re: Re: RE: Re: RE: Re: Strange behaviour on Orbeon 3.7.1
|
|
Hello Alex / Erik,
I think I see what you're getting at.
What would I need to make this construction work? Could I use an xforms:group for this?
For clarity: - I have a set of buttons on a xform - After entering some data and submitting the initial xform, some additional (instance) data is added to the form displayed (works fine!) (source: an XPL) - Depending on the data in the instance, I want to either hide or disable some of those buttons
Thanks again, Robin -----Original message----- -- 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 |
Re: Re: Re: RE: Re: RE: Re: Strange behaviour on Orbeon 3.7.1
|
Administrator
|
Robin,
I am not sure that we correctly understood your problem. Could you attach here a simple example that shows what you are trying to do, and what doesn't work the way you expect? Alex On Wed, Feb 24, 2010 at 10:40 PM, Robin Diederen <[hidden email]> wrote: > Hello Alex / Erik, > > > > I think I see what you're getting at. > > > > What would I need to make this construction work? Could I use an > xforms:group for this? > > > > For clarity: > > - I have a set of buttons on a xform > > - After entering some data and submitting the initial xform, some additional > (instance) data is added to the form displayed (works fine!) (source: an > XPL) > > - Depending on the data in the instance, I want to either hide or disable > some of those buttons > > > > Thanks again, Robin > > > -----Original message----- > From: Alessandro Vernet <[hidden email]> > Sent: Thu 25-02-2010 00:22 > To: [hidden email]; > Subject: [ops-users] Re: Re: RE: Re: RE: Re: Strange behaviour on Orbeon > 3.7.1 > > Robin, > > To clarify, like Erik said, your instance will be submitted, and in > the instance the non-relevant nodes will be pruned. > > Alex > > On Wed, Feb 24, 2010 at 8:17 AM, Erik Bruchez <[hidden email]> wrote: >> Robin, >> >> A submission always submits instance content, not XForms constructs >> (such as binds or models or controls). >> >> -Erik >> >> On Wed, Feb 24, 2010 at 2:06 PM, Robin Diederen <[hidden email]> wrote: >>> 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 >>> >>> >> >> >> -- >> 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
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
wrong URL for resource rendering if using different "root context"
|
|
In reply to this post by Robin Diederen
Hi,
We deployed Orbeon on Liferay in JBoss Container. This worked fine until we changed the root context from "localhost:8080/" to "localhost:8080/myportal/" Neither the orbeon samples nor our own portlets rendered correctly. We saw the famous Loading... An error has occurred You may want to try one of the following: .... Now the orbeon samples work again, but still our own portlets show the error above. The steps we did so far: -adding to liferay's jboss-web.xml <context-root>myportal </context-root> -adding to liferay's portal-ext.properties portal.ctx=/myportal Then we reached the point mentionend above. -adding to liferay's web.xml <context-param> <param-name>root_path</param-name> <param-value>/myportal </param-value> </context-param> made the Orbeon samples working again, (hurrah) but our own portlets in our webui.war still show the error. I have no idea, what happens and would be glad if anybody helped me. Looking at the source of a orbeon sample html page, I see that resources are loaded from href="/orbeon/xforms-server/xforms-yuicalendar-min.css" The portlets in our own webui.war try to load the same resource from src="/myportal/orbeon/xforms-server/xforms-yuicalendar-min.js"> the additional "myportal" in the path is the problem and I don't know how to solve this. Can anybody please help? Thanks a lot Hubert -- 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 |
Antw: wrong URL for resource rendering if using different "root context" > BUG in URLRewriterUtils.getClientCont
|
|
Hey,
I investigated the issue. For me it looks like a bug of org.orbeon.oxf.util.URLRewriterUtils.getClientContextPath(). Hope Orbeon specialists can help with this problem: The resource URLs like /xforms-server/xforms-yuicalendar-min.css get rewritten depending on the context. In separate deploment URLRewriterUtils.getClientContextPath() builds the client context path like that: javax.servlet.forward.context_path + orbeon context path javax.servlet.forward.context_path is our portal context-root "myportal". So all resources get rewritten with /myportal/Orbeon/ and our resource becomes: src="/myportal/orbeon/xforms-server/xforms-yuicalendar-min.js" But javax.servlet.forward.context_path is not the source context path of the Orbeon resources. So the resources are not found and the source code can't get rendered properly. With a hack I solved the problem, by setting "oxf.xforms.renderer.deployment" to "integrated" in OrbeonXFormsFilter. So URLRewriterUtils.getClientContextPath() doesn't build the client context path with the source context path red out of "javax.servlet.forward.context_path". But this is not the solution and I dont know the side effects of this hack. Hope Orbeon specialists know better ways to solve the problem? Karolin >>> "Hubert Felber" <[hidden email]> 3/2/2010 10:48 >>> Hi, We deployed Orbeon on Liferay in JBoss Container. This worked fine until we changed the root context from "localhost:8080/" to "localhost:8080/myportal/" Neither the orbeon samples nor our own portlets rendered correctly. We saw the famous Loading... An error has occurred You may want to try one of the following: .... Now the orbeon samples work again, but still our own portlets show the error above. The steps we did so far: -adding to liferay's jboss-web.xml <context-root>myportal </context-root> -adding to liferay's portal-ext.properties portal.ctx=/myportal Then we reached the point mentionend above. -adding to liferay's web.xml <context-param> <param-name>root_path</param-name> <param-value>/myportal </param-value> </context-param> made the Orbeon samples working again, (hurrah) but our own portlets in our webui.war still show the error. I have no idea, what happens and would be glad if anybody helped me. Looking at the source of a orbeon sample html page, I see that resources are loaded from href="/orbeon/xforms-server/xforms-yuicalendar-min.css" The portlets in our own webui.war try to load the same resource from src="/myportal/orbeon/xforms-server/xforms-yuicalendar-min.js"> the additional "myportal" in the path is the problem and I don't know how to solve this. Can anybody please help? Thanks a lot Hubert -- 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 |
BUG in URLRewriterUtils.getClientCont
|
|
Hello,
I still dont found any solution for the problem and assume, that the problem is how URLRewriterUtils creates the client context path. (problem described below) Because of the wrong resource urls, created by URLRewriterUtils my XForms dont render any more: wrong resource url with custom context root "myportal": src="/myportal/orbeon/xforms-server/xforms-yuicalendar-min.js" resource url with default context root: src="/orbeon/xforms-server/xforms-yuicalendar-min.js" I hope somebody can help? Thank you very much, Karolin >>> "Karolin Krieg" <[hidden email]> 3/3/2010 10:29 >>> Hey, I investigated the issue. For me it looks like a bug of org.orbeon.oxf.util.URLRewriterUtils.getClientContextPath(). Hope Orbeon specialists can help with this problem: The resource URLs like /xforms-server/xforms-yuicalendar-min.css get rewritten depending on the context. In separate deploment URLRewriterUtils.getClientContextPath() builds the client context path like that: javax.servlet.forward.context_path + orbeon context path javax.servlet.forward.context_path is our portal context-root "myportal". So all resources get rewritten with /myportal/Orbeon/ and our resource becomes: src="/myportal/orbeon/xforms-server/xforms-yuicalendar-min.js" But javax.servlet.forward.context_path is not the source context path of the Orbeon resources. So the resources are not found and the source code can't get rendered properly. With a hack I solved the problem, by setting "oxf.xforms.renderer.deployment" to "integrated" in OrbeonXFormsFilter. So URLRewriterUtils.getClientContextPath() doesn't build the client context path with the source context path red out of "javax.servlet.forward.context_path". But this is not the solution and I dont know the side effects of this hack. Hope Orbeon specialists know better ways to solve the problem? Karolin >>> "Hubert Felber" <[hidden email]> 3/2/2010 10:48 >>> Hi, We deployed Orbeon on Liferay in JBoss Container. This worked fine until we changed the root context from "localhost:8080/" to "localhost:8080/myportal/" Neither the orbeon samples nor our own portlets rendered correctly. We saw the famous Loading... An error has occurred You may want to try one of the following: .... Now the orbeon samples work again, but still our own portlets show the error above. The steps we did so far: -adding to liferay's jboss-web.xml <context-root>myportal </context-root> -adding to liferay's portal-ext.properties portal.ctx=/myportal Then we reached the point mentionend above. -adding to liferay's web.xml <context-param> <param-name>root_path</param-name> <param-value>/myportal </param-value> </context-param> made the Orbeon samples working again, (hurrah) but our own portlets in our webui.war still show the error. I have no idea, what happens and would be glad if anybody helped me. Looking at the source of a orbeon sample html page, I see that resources are loaded from href="/orbeon/xforms-server/xforms-yuicalendar-min.css" The portlets in our own webui.war try to load the same resource from src="/myportal/orbeon/xforms-server/xforms-yuicalendar-min.js"> the additional "myportal" in the path is the problem and I don't know how to solve this. Can anybody please help? Thanks a lot Hubert -- 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 |
«
Return to Orbeon Forms community mailing list
|
1 view|%1 views
| Free forum by Nabble | Edit this page |