Seems a nice feature to implement!
-Original Message-
From: Mike Moulton
To: [EMAIL PROTECTED]
Sent: 10/4/2003 3:15 AM
Subject: [Mav-user] Proposed XSLTransform Modification
This is a repost as I sent it yesterday and it never showed up. Sorry
if it's a duplicate for anyone.
I would like to propose a minor modification to maverick that would
allow XSL templates used in a XSLTransform to be loaded from a
java.net.URL. Additionally, any template that was loaded from a 'file:'
URL could optionally be monitored, to have the cache (if used) updated
if and when the monitored file is changed.
An example of how the change would effect the maverick.xml file is
shown below:
command name=index
controller class=some.controller.package.Index /
view name=success type=domify
transform type=xslt
path=file:/home/mmoulton/xsl/index.xsl monitored=true/
transform type=xslt
path=file:/home/mmoulton/xsl/template.xsl /
/view
/command
In this example the index.xsl would be loaded from the local path of
/home/mmoulton/xsl, if this file is modified on the system, then those
changes would be reflected in the compiled XSL. Similarly the
template.xsl would be loaded from the local filesystem, however changes
would not be detected and a maverick config reload / app server restart
would be required to reflect any changes.
Is this functionally beneficial to maverick as a whole?
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
[INVALID FOOTER]
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
[INVALID FOOTER]
