Orbeon Forms community mailing list

Problem understanding PageFlowController matchers

Classic

List

Threaded

8 messages Options

Gunzenreiner Simon

Problem understanding PageFlowController matchers

Hello

I am trying to navigate to a .xhtml page, bug giving this the .html extension. I first tried the following config in page-flow.xml:

… but this resulted in a 404.

Then I tried the perl5-matcher, expecting this to work:

<page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"

view="${1}/${2}.xhtml"

matcher="oxf:perl5-matcher"/>

… but again, 404.

… only the following matching expression works (note: not using a file extension in the path-info):

Does anybody understand this behavior?

Best regards,

Simon

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

Louis Ratzesberger-2

Re: Problem understanding PageFlowController matchers

Hi Simon,

The page flow controller has elements that match filename extensions,
and deliver those directly without any processing. e.g.:

<files
path-info="(?!/([^/]+)/service/).+\.gif|css|pdf|json|js|png|jpg|xsd|htc|ico|swf|html|txt)"
matcher="oxf:perl5-matcher"/>

which will match the various files in the /.../service/ request path.

This is helpful if you want to mix .html files that ARE NOT view files
to be processed as XForms or XSLT files.

Per the "Cool URI" recommendation, allow me to suggest that you don't
use file extensions on pages that you want to process as XForms.

http://www.w3.org/Provider/Style/URI

The page flow controller will deliver the content as html or xhtml
(which one is also evolving as all the browsers get up to spec.)

If you must maintain compatibility with an existing application,
perhaps using a web server front-end to rewrite the URL is an option
-- assuming you want to eventually use the W3 recommendation.

HTH,
Hank

Quoting Gunzenreiner Simon <[hidden email]>:

> Hello
>
> I am trying to navigate to a .xhtml page, bug giving this the .html
> extension. I first tried the following config in page-flow.xml:
>
> <page path-info="/order/status/index.html" view="status/index.xhtml" />
> ... but this resulted in a 404.
>
> Then I tried the perl5-matcher, expecting this to work:
>
> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
> view="${1}/${2}.xhtml"
> matcher="oxf:perl5-matcher"/>
> ... but again, 404.
>
> ... only the following matching expression works (note: not using a file
> extension in the path-info):
> <page path-info="/order/status/index" view="status/index.xhtml" />
>
> Does anybody understand this behavior?
>
> Best regards,
> Simon
>
>

--
Hank Ratzesberger
[hidden 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
OW2 mailing lists service home page: http://www.ow2.org/wws

Gunzenreiner Simon

AW: Re: Problem understanding PageFlowController matchers

Hi Louis

Are you saying that file extensions would not be supported by the matchers? According to the documentation (http://www.orbeon.com/orbeon/doc/reference-page-flow#matchers) I should be able to apply matching expressions as well to URIs with file extensions.

Why would a matching expression like this not work?

<page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
view="${1}/${2}.xhtml"
matcher="oxf:perl5-matcher"/>

Regards,
Simon
-----Ursprüngliche Nachricht-----
Von: Louis Ratzesberger [mailto:[hidden email]]
Gesendet: Montag, 2. August 2010 20:37
An: [hidden email]
Betreff: [ops-users] Re: Problem understanding PageFlowController matchers

Hi Simon,

The page flow controller has elements that match filename extensions, and deliver those directly without any processing. e.g.:

<files
path-info="(?!/([^/]+)/service/).+\.gif|css|pdf|json|js|png|jpg|xsd|htc|ico|swf|html|txt)"
matcher="oxf:perl5-matcher"/>

which will match the various files in the /.../service/ request path.

This is helpful if you want to mix .html files that ARE NOT view files to be processed as XForms or XSLT files.

Per the "Cool URI" recommendation, allow me to suggest that you don't use file extensions on pages that you want to process as XForms.

http://www.w3.org/Provider/Style/URI

The page flow controller will deliver the content as html or xhtml (which one is also evolving as all the browsers get up to spec.)

If you must maintain compatibility with an existing application, perhaps using a web server front-end to rewrite the URL is an option
-- assuming you want to eventually use the W3 recommendation.

HTH,
Hank

Quoting Gunzenreiner Simon <[hidden email]>:

> Hello
>
> I am trying to navigate to a .xhtml page, bug giving this the .html
> extension. I first tried the following config in page-flow.xml:
>
> <page path-info="/order/status/index.html" view="status/index.xhtml"
> /> ... but this resulted in a 404.
>
> Then I tried the perl5-matcher, expecting this to work:
>
> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
> view="${1}/${2}.xhtml"
> matcher="oxf:perl5-matcher"/>
> ... but again, 404.
>
> ... only the following matching expression works (note: not using a
> file extension in the path-info):
> <page path-info="/order/status/index" view="status/index.xhtml" />
>
> Does anybody understand this behavior?
>
> Best regards,
> Simon
>
>

Louis Ratzesberger-2

Re: AW: Re: Problem understanding PageFlowController matchers

Hi Simon,

Sorry, no, I didn't mean to suggest it would not work, and it looks
like it should. However, it sounds like you are encountering the
Tomcat 404 page and not the page-flow controller error, which would
have the Orbeon error page styling and say no match could be found.

If the file you are looking for is 'index.html' then it may be your
Tomcat welcome files list or another aspect of the server
configuration that is taking precedence over the page flow controller.

My best guess at this point...

Cheers,
Louis (Hank) Ratzesberger

Quoting Gunzenreiner Simon <[hidden email]>:

> Hi Louis
>
> Are you saying that file extensions would not be supported by the
> matchers? According to the documentation
> (http://www.orbeon.com/orbeon/doc/reference-page-flow#matchers) I
> should be able to apply matching expressions as well to URIs with
> file extensions.
>
> Why would a matching expression like this not work?
>
> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
> view="${1}/${2}.xhtml"
> matcher="oxf:perl5-matcher"/>
>
> Regards,
> Simon
> -----Ursprüngliche Nachricht-----
> Von: Louis Ratzesberger [mailto:[hidden email]]
> Gesendet: Montag, 2. August 2010 20:37
> An: [hidden email]
> Betreff: [ops-users] Re: Problem understanding PageFlowController matchers
>
> Hi Simon,
>
> The page flow controller has elements that match filename
> extensions, and deliver those directly without any processing. e.g.:
>
> <files
> path-info="(?!/([^/]+)/service/).+\.gif|css|pdf|json|js|png|jpg|xsd|htc|ico|swf|html|txt)"
> matcher="oxf:perl5-matcher"/>
>
> which will match the various files in the /.../service/ request path.
>
> This is helpful if you want to mix .html files that ARE NOT view
> files to be processed as XForms or XSLT files.
>
> Per the "Cool URI" recommendation, allow me to suggest that you
> don't use file extensions on pages that you want to process as XForms.
>
> http://www.w3.org/Provider/Style/URI
>
> The page flow controller will deliver the content as html or xhtml
> (which one is also evolving as all the browsers get up to spec.)
>
> If you must maintain compatibility with an existing application,
> perhaps using a web server front-end to rewrite the URL is an option
> -- assuming you want to eventually use the W3 recommendation.
>
> HTH,
> Hank
>
> Quoting Gunzenreiner Simon <[hidden email]>:
>
>> Hello
>>
>> I am trying to navigate to a .xhtml page, bug giving this the .html
>> extension. I first tried the following config in page-flow.xml:
>>
>> <page path-info="/order/status/index.html" view="status/index.xhtml"
>> /> ... but this resulted in a 404.
>>
>> Then I tried the perl5-matcher, expecting this to work:
>>
>> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
>> view="${1}/${2}.xhtml"
>> matcher="oxf:perl5-matcher"/>
>> ... but again, 404.
>>
>> ... only the following matching expression works (note: not using a
>> file extension in the path-info):
>> <page path-info="/order/status/index" view="status/index.xhtml" />
>>
>> Does anybody understand this behavior?
>>
>> Best regards,
>> Simon
>>
>>
>
>
>
> --
> Hank Ratzesberger
> [hidden email]
>
>

Alessandro Vernet

Re: AW: Re: Problem understanding PageFlowController matchers

Administrator

In reply to this post by Gunzenreiner Simon

Simon,

As mentioned by Hank, the .html files are configured to be served from
the resources directly. I.e. if you have a request for /a/b.html, the
page flow looks for resources/a/b.html. This is before of the <files>
in the top-level page-flow.xml. Remove the matching for .html there,
and you can then have a <page path-info="/xforms-hello/view.html"
view="view.xhtml"/> in your app page flow.

Alex

On Mon, Aug 2, 2010 at 11:47 PM, Gunzenreiner Simon
<[hidden email]> wrote:

> Hi Louis
>
> Are you saying that file extensions would not be supported by the matchers? According to the documentation (http://www.orbeon.com/orbeon/doc/reference-page-flow#matchers) I should be able to apply matching expressions as well to URIs with file extensions.
>
> Why would a matching expression like this not work?
>
> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
> view="${1}/${2}.xhtml"
> matcher="oxf:perl5-matcher"/>
>
> Regards,
> Simon
> -----Ursprüngliche Nachricht-----
> Von: Louis Ratzesberger [mailto:[hidden email]]
> Gesendet: Montag, 2. August 2010 20:37
> An: [hidden email]
> Betreff: [ops-users] Re: Problem understanding PageFlowController matchers
>
> Hi Simon,
>
> The page flow controller has elements that match filename extensions, and deliver those directly without any processing. e.g.:
>
> <files
> path-info="(?!/([^/]+)/service/).+\.gif|css|pdf|json|js|png|jpg|xsd|htc|ico|swf|html|txt)"
> matcher="oxf:perl5-matcher"/>
>
> which will match the various files in the /.../service/ request path.
>
> This is helpful if you want to mix .html files that ARE NOT view files to be processed as XForms or XSLT files.
>
> Per the "Cool URI" recommendation, allow me to suggest that you don't use file extensions on pages that you want to process as XForms.
>
> http://www.w3.org/Provider/Style/URI
>
> The page flow controller will deliver the content as html or xhtml (which one is also evolving as all the browsers get up to spec.)
>
> If you must maintain compatibility with an existing application, perhaps using a web server front-end to rewrite the URL is an option
> -- assuming you want to eventually use the W3 recommendation.
>
> HTH,
> Hank
>
> Quoting Gunzenreiner Simon <[hidden email]>:
>
>> Hello
>>
>> I am trying to navigate to a .xhtml page, bug giving this the .html
>> extension. I first tried the following config in page-flow.xml:
>>
>> <page path-info="/order/status/index.html" view="status/index.xhtml"
>> /> ... but this resulted in a 404.
>>
>> Then I tried the perl5-matcher, expecting this to work:
>>
>> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
>> view="${1}/${2}.xhtml"
>> matcher="oxf:perl5-matcher"/>
>> ... but again, 404.
>>
>> ... only the following matching expression works (note: not using a
>> file extension in the path-info):
>> <page path-info="/order/status/index" view="status/index.xhtml" />
>>
>> Does anybody understand this behavior?
>>
>> Best regards,
>> Simon
>>
>>
>
>
>
> --
> Hank Ratzesberger
> [hidden 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
> 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

Gunzenreiner Simon

AW: Re: AW: Re: Problem understanding PageFlowController matchers

Hi Alex, Hank

This is exactly what I did yesterday evening! Thanks for the tip anyway, it works now.

Best regards
Simon

-----Ursprüngliche Nachricht-----
Von: Alessandro Vernet [mailto:[hidden email]]
Gesendet: Mittwoch, 4. August 2010 01:34
An: ops-users
Betreff: [ops-users] Re: AW: Re: Problem understanding PageFlowController matchers

Simon,

As mentioned by Hank, the .html files are configured to be served from the resources directly. I.e. if you have a request for /a/b.html, the page flow looks for resources/a/b.html. This is before of the <files> in the top-level page-flow.xml. Remove the matching for .html there, and you can then have a <page path-info="/xforms-hello/view.html"
view="view.xhtml"/> in your app page flow.

Alex

On Mon, Aug 2, 2010 at 11:47 PM, Gunzenreiner Simon <[hidden email]> wrote:

> Hi Louis
>
> Are you saying that file extensions would not be supported by the matchers? According to the documentation (http://www.orbeon.com/orbeon/doc/reference-page-flow#matchers) I should be able to apply matching expressions as well to URIs with file extensions.
>
> Why would a matching expression like this not work?
>
> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
> view="${1}/${2}.xhtml"
> matcher="oxf:perl5-matcher"/>
>
> Regards,
> Simon
> -----Ursprüngliche Nachricht-----
> Von: Louis Ratzesberger [mailto:[hidden email]]
> Gesendet: Montag, 2. August 2010 20:37
> An: [hidden email]
> Betreff: [ops-users] Re: Problem understanding PageFlowController
> matchers
>
> Hi Simon,
>
> The page flow controller has elements that match filename extensions, and deliver those directly without any processing. e.g.:
>
> <files
> path-info="(?!/([^/]+)/service/).+\.gif|css|pdf|json|js|png|jpg|xsd|htc|ico|swf|html|txt)"
> matcher="oxf:perl5-matcher"/>
>
> which will match the various files in the /.../service/ request path.
>
> This is helpful if you want to mix .html files that ARE NOT view files to be processed as XForms or XSLT files.
>
> Per the "Cool URI" recommendation, allow me to suggest that you don't use file extensions on pages that you want to process as XForms.
>
> http://www.w3.org/Provider/Style/URI
>
> The page flow controller will deliver the content as html or xhtml
> (which one is also evolving as all the browsers get up to spec.)
>
> If you must maintain compatibility with an existing application,
> perhaps using a web server front-end to rewrite the URL is an option
> -- assuming you want to eventually use the W3 recommendation.
>
> HTH,
> Hank
>
> Quoting Gunzenreiner Simon <[hidden email]>:
>
>> Hello
>>
>> I am trying to navigate to a .xhtml page, bug giving this the .html
>> extension. I first tried the following config in page-flow.xml:
>>
>> <page path-info="/order/status/index.html" view="status/index.xhtml"
>> /> ... but this resulted in a 404.
>>
>> Then I tried the perl5-matcher, expecting this to work:
>>
>> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
>> view="${1}/${2}.xhtml"
>> matcher="oxf:perl5-matcher"/>
>> ... but again, 404.
>>
>> ... only the following matching expression works (note: not using a
>> file extension in the path-info):
>> <page path-info="/order/status/index" view="status/index.xhtml" />
>>
>> Does anybody understand this behavior?
>>
>> Best regards,
>> Simon
>>
>>
>
>
>
> --
> Hank Ratzesberger
> [hidden 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
> 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

Alessandro Vernet

Re: Problem understanding PageFlowController matchers

Administrator

Simon,

I am glad changing the <files> in the page flow worked; thank you for
the update.

Alex

On Tuesday, August 3, 2010, Gunzenreiner Simon
<[hidden email]> wrote:

> Hi Alex, Hank
>
> This is exactly what I did yesterday evening! Thanks for the tip anyway, it works now.
>
> Best regards
> Simon
>
> -----Ursprüngliche Nachricht-----
> Von: Alessandro Vernet [mailto:[hidden email]]
> Gesendet: Mittwoch, 4. August 2010 01:34
> An: ops-users
> Betreff: [ops-users] Re: AW: Re: Problem understanding PageFlowController matchers
>
> Simon,
>
> As mentioned by Hank, the .html files are configured to be served from the resources directly. I.e. if you have a request for /a/b.html, the page flow looks for resources/a/b.html. This is before of the <files> in the top-level page-flow.xml. Remove the matching for .html there, and you can then have a <page path-info="/xforms-hello/view.html"
> view="view.xhtml"/> in your app page flow.
>
> Alex
>
> On Mon, Aug 2, 2010 at 11:47 PM, Gunzenreiner Simon <[hidden email]> wrote:
>> Hi Louis
>>
>> Are you saying that file extensions would not be supported by the matchers? According to the documentation (http://www.orbeon.com/orbeon/doc/reference-page-flow#matchers) I should be able to apply matching expressions as well to URIs with file extensions.
>>
>> Why would a matching expression like this not work?
>>
>> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
>> view="${1}/${2}.xhtml"
>> matcher="oxf:perl5-matcher"/>
>>
>> Regards,
>> Simon
>> -----Ursprüngliche Nachricht-----
>> Von: Louis Ratzesberger [mailto:[hidden email]]
>> Gesendet: Montag, 2. August 2010 20:37
>> An: [hidden email]
>> Betreff: [ops-users] Re: Problem understanding PageFlowController
>> matchers
>>
>> Hi Simon,
>>
>> The page flow controller has elements that match filename extensions, and deliver those directly without any processing. e.g.:
>>
>> <files
>> path-info="(?!/([^/]+)/service/).+\.gif|css|pdf|json|js|png|jpg|xsd|htc|ico|swf|html|txt)"
>> matcher="oxf:perl5-matcher"/>
>>
>> which will match the various files in the /.../service/ request path.
>>
>> This is helpful if you want to mix .html files that ARE NOT view files to be processed as XForms or XSLT files.
>>
>> Per the "Cool URI" recommendation, allow me to suggest that you don't use file extensions on pages that you want to process as XForms.
>>
>> http://www.w3.org/Provider/Style/URI
>>
>> The page flow controller will deliver the content as html or xhtml
>> (which one is also evolving as all the browsers get up to spec.)
>>
>> If you must maintain compatibility with an existing application,
>> perhaps using a web server front-end to rewrite the URL is an option
>> -- assuming you want to eventually use the W3 recommendation.
>>
>> HTH,
>> Hank
>>
>> Quoting Gunzenreiner Simon <[hidden email]>:
>>
>>> Hello
>>>
>>> I am trying to navigate to a .xhtml page, bug giving this the .html
>>> extension. I first tried the following config in page-flow.xml:
>>>
>>> <page path-info="/order/status/index.html" view="status/index.xhtml"
>>> /> ... but this resulted in a 404.
>>>
>>> Then I tried the perl5-matcher, expecting this to work:
>>>
>>> <page path-info="/order/([_A-Za-z\-0-9]+)/([_A-Za-z\-0-9]+)\.html"
>>> view="${1}/${2}.xhtml"
>>> matcher="oxf:perl5-matcher"/>
>>> ... but again, 404.
>>>
>>> ... only the following matching expression works (note: not using a
>>> file extension in the path-info):
>>> <page path-info="/order/status/index" view="status/index.xhtml" />
>>>
>>> Does anybody understand this behavior?
>>>
>>> Best regards,
>>> Simon
>>>
>>>
>>
>>
>>
>> --
>> Hank Ratzesberger
>> [hidden email]
>>
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email] mailing list.
>> To unsubscribe: mailto:

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

Alessandro Vernet

Re: Problem understanding PageFlowController matchers

Administrator

In reply to this post by Gunzenreiner Simon

Simon,

I am glad changing the <files> in the page flow worked; thank you for
the update.

Alex

On Tuesday, August 3, 2010, Gunzenreiner Simon
<[hidden email]> wrote:

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet