Problem developing dynamic page-flow navigation using internal xml submission and matchers

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem developing dynamic page-flow navigation using internal xml submission and matchers

Tom Grahame
Dear list,

I am trying to create dynamic navigation using logic implemented in the page-flow, however I am facing problems selecting a page that uses matchers by passing xml to it internally from a page/action/result element.

I have created an app that recreates the problem and it can be dropped into the default apps folder of Orbeon.
matcher-nav.zip

When I attempt to access the following page in my browser:
http://localhost:8080/orbeon/matcher-nav/add/journal-article/

I expect the dummy logic in the page-flow to be executed and the browser to be redirected for me to see:
http://localhost:8080/orbeon/matcher-nav/add/journal-article/
in the address bar.

Instead the page-flow logic executes and I see this in the address bar:
http://localhost:8080/orbeon/matcher-nav/add//?%24instance=X2ztn...

It is as if the xsl in the result element of lines 22-24 of page-flow.xml is not passed, or evaluates to null.

In my example I have included some logic and pipelines that don't do much but do represent the occurance of real logic in my live app.

I have read the documentation here:
http://www.orbeon.com/ops/doc/reference-page-flow#navigating-to-matchers-pages
and tried to build my app accordingly, but without much success.

Could anyone offer any suggestions?

Thanks,

Tom
Reply | Threaded
Open this post in threaded view
|

Re: Problem developing dynamic page-flow navigation using internal xml submission and matchers

Tom Grahame
Tom Grahame wrote
Dear list,

I am trying to create dynamic navigation using logic implemented in the page-flow, however I am facing problems selecting a page that uses matchers by passing xml to it internally from a page/action/result element.

I have created an app that recreates the problem and it can be dropped into the default apps folder of Orbeon.
matcher-nav.zip
Can anyone reproduce this? Even if a fix isn't provided it would be nice to know I am going in the right direction.

Thanks,

Tom
Reply | Threaded
Open this post in threaded view
|

Re: Problem developing dynamic page-flow navigation using internal xml submission and matchers

Alessandro Vernet
Administrator
In reply to this post by Tom Grahame
Hi Tom,

On Mar 20, 2009, at 4:15 AM, Tom Grahame wrote:

> I am trying to create dynamic navigation using logic implemented in  
> the
> page-flow, however I am facing problems selecting a page that uses  
> matchers
> by passing xml to it internally from a page/action/result element.

Sorry for the delay.

I reproduced the problem. There was an xmlns="" missing on the  
<content-type> (otherwise that element will be in the PFC namespace),  
but that is not enough to solve the problem. This is a tricky case and  
we haven't used this in a while. So I am either missing something, or  
this has been broken at some point. I created bug, linked here for  
reference:

http://forge.ow2.org/tracker/index.php?func=detail&aid=313592&group_id=168&atid=350207

As a workaround, you can use a redirect processor in XPL. Nowadays, we  
tend to implement this directly in XForms and then we would use an  
<xforms:load> from XForms.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
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
Reply | Threaded
Open this post in threaded view
|

Re: Problem developing dynamic page-flow navigation using internal xml submission and matchers

Tom Grahame
Hi Alex,

Thanks for examining my test case.

I have resolved this by hard-coding extra page ids in page-flow.xml and referring to them explicitly.
This is not elegant, but I believe keeps the logic inside of the page flow - as per recommendations ;)

Thanks for adding the bug also.

Regards,

Tom

Alessandro Vernet wrote
Hi Tom,

On Mar 20, 2009, at 4:15 AM, Tom Grahame wrote:

> I am trying to create dynamic navigation using logic implemented in  
> the
> page-flow, however I am facing problems selecting a page that uses  
> matchers
> by passing xml to it internally from a page/action/result element.

Sorry for the delay.

I reproduced the problem. There was an xmlns="" missing on the  
<content-type> (otherwise that element will be in the PFC namespace),  
but that is not enough to solve the problem. This is a tricky case and  
we haven't used this in a while. So I am either missing something, or  
this has been broken at some point. I created bug, linked here for  
reference:

http://forge.ow2.org/tracker/index.php?func=detail&aid=313592&group_id=168&atid=350207

As a workaround, you can use a redirect processor in XPL. Nowadays, we  
tend to implement this directly in XForms and then we would use an  
<xforms:load> from XForms.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet



--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws


-----
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet