Eric van der Vlist wrote:
The first thing that bites me is that all the relative references in my page-flow.xml are now raising class java.net.MalformedURLException / no protocol exceptions.
That seems pretty natural since the page flow is now a result in a pipe and has no base URI.
Yes, because the PFC is generated from XSLT.
A clean way to fix that would be to add an xml:base attribute in page-flow.xml.
Yes, I think that would be good, and not too difficult to fix IMO:
o Fix the schema to allow xml:base on every element o Make sure the attribute is used when relative URLs are resolved
http://sourceforge.net/tracker/index.php?func=detail&aid=1116332&group_id=116683&atid=675663
There was a thread earlier on this list mentioning that xml:base attributes are not permitted per the current schema (and I can confirm that!), but I am also wondering if, beyond that restriction, the attribute would be handled properly by the PFC controller (in other words, would that work if I changed the schema?).
No, it doesn't allow xml:base, and won't process it either.
Other workarounds are, of course, either to replace my relative URIs by absolute ones in page-flow.xml or to rewrite them in the filtering transformation.
Exactly, just prefix them with oxf: or file:.
-Erik
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
