[
https://issues.apache.org/activemq/browse/SM-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47615#action_47615
]
Jon Brisbin commented on SM-1704:
---------------------------------
I actually have a need for something similar and I'm wondering if it wouldn't
be a good idea to create an OSGi service like Felix's File watcher that could
handle checking modification times for file: and classpath: resources, and
hashing content for other protocols? One could check for an HTTP 304 NOT
MODIFIED or pull the entire content and hash it. The interval for this would
need to be longer than the reload interval for local resources, but it might be
good to have this service available to any bundle that needed it, not just
servicemix-saxon. Or maybe baby-step it and create a file watcher inside the
saxon SE first, then it extend it to other bundles later.
> Allow for automatic reload of XSLT file when changes are made to it
> -------------------------------------------------------------------
>
> Key: SM-1704
> URL: https://issues.apache.org/activemq/browse/SM-1704
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-saxon
> Affects Versions: servicemix-saxon-2008.01
> Reporter: Raul Kripalani
>
> When the XSLT file used for the transformation resides in the filesystem
> ("file:/" resource), the servicemix-saxon component should detect when
> changes are made to the stylesheet and should reload it on-the-fly. This
> feature should be switchable by the user via a flag in the xbean.xml file.
> (This behaviour is not suitable in all environments...). Ideally, the scan
> interval should be user-configurable too.
> Also, a method should be exposed via JMX to trigger the reload of the XSLT,
> for those cases in which the user disables the automatic reloading capability.
> Currently, the SA has to be redeployed or ServiceMix has to be restarted in
> order to reload a stylesheet.
> Please see
> http://www.nabble.com/Reloadable-XSLT-in-servicemix-saxon-td20678812.html for
> more details and workaround in the meantime.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
