Hi,
We store documents in a database without a suffix but can specify the
mime-type.
We found this simple and matcher method works if the document 12345 is
set as mime-type text/xml
<page path-info="/12345" view="
http://localhost/doc/12345"/>
<page path-info="/frm/([^/]+)" matcher="oxf:perl5-matcher" view="
http://localhost/doc/$
{1}"/>
Ideally I would like to just pass through the whole url but I suspect
the matcher has no access
to the parameters of the url. This would be great if it was possible ..
user get request
/frm/12345?url=/db/v7%63p1=abcd%38p2=efgh
to make view result as ..
view=
http://localhost/doc/12345?url=/db/v7%63p1=abcd%38p2=efghperhaps with something like
<page path-info="/frm/([^/]+)\?([^/])" matcher="oxf:perl5-matcher"
view="
http://localhost/doc/${1}?${2}"/>
If it is not possible there is still scope with xsl where
http://localhost/doc/12345
is an xsl document eg
<page path-info="/frm/([^/]+)" matcher="oxf:perl5-matcher" view="
http://localhost/doc/$
{1}" default-submission="url.xml">
<setvalue ref="/get/url" parameter="url"/>
</page>
<!-- file: url.xml -->
<get>
<url/>
</get>
However the problem I've encountered is that a mime-type of 'text/xsl'
is not sufficient to tell PFC
http://localhost/doc/12345 is an xsl
document.
Any suggestions greatly appreciated.
Thank you,
John Russell.
--
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