I had a need for something similar and created a patch against trunk
that allows you to specify that a particular XSLT or XQuery needs to
be reloaded every time. This way it works for all protocols (like
those of us who define an http:// resource location in Subversion for
development files), not just local ones.
But it looks like they've got a workable solution, so that's good. We
must have created our issues at the same time. :)
Thanks!
Jon Brisbin
http://jbrisbin.com
On Nov 25, 2008, at 6:50 AM, Guillaume Nodet wrote:
That makes sense. Please raise a JIRA for this improvement.
On Tue, Nov 25, 2008 at 11:44 AM, raulvk.soa <[EMAIL PROTECTED]>
wrote:
Hi everyone,
We are using the servicemix-saxon Service Unit in our development.
The
stylesheet comes from the file system, therefore the xbean.xml
points to a
file:/// location.
When we make changes to the XSLT file we want those changes to be
effective
without having to restart the ESB. I have tried Stopping and
Shutting Down
the SA from the JMX console, then Restarting it, but it still uses
the
previous version. It's like it is not letting go of the compiled
stylesheet.
Does anyone know if there is a way of making the component get hold
of the
updated version of the stylesheet without having to restart the ESB
or
redeploy the SA?
We expect to make changes to the transformations while the ESB is
running,
so ideally the servicemix-saxon component should detect that the
file has
been modified and should reload it dynamically. As of today, I
believe that
the component does not support this functionality... Are there any
plans of
introducing it in future versions?
Many thanks,
Raul.
--
View this message in context:
http://www.nabble.com/Reloadable-XSLT-in-servicemix-saxon-tp20678812p20678812.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
