Raul, I have a similar problem. My solution was to 'touch' the service assembly in the deploy/hotdeploy directory. This causes servicemix to redeploy the service assembly and re-read the XSLT. If you really can't redeploy your main service assembly, consider putting the XSLT in its own separate service assembly.
- Jeff On Tue, Nov 25, 2008 at 4:50 AM, Guillaume Nodet <[EMAIL PROTECTED]> 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 >
