Ashwin, Our requirement is, given an XSLT file that is located in the filesystem, if changes are made to the file, the servicemix-saxon component should detect them at runtime and reload and recompile the stylesheet, without having to restart the ESB.
I believe that your suggestion is suitable for when the requirement is to select an XSLT file out of many based on some condition. Thanks anyway! Ashwin Karpe wrote: > > Raul, > > The best workaround to accomplish this for now would be to develop a > Servicemix bean that can select an XSLT transform file based onthe > criteria you would like to apply. This could be far more flexible than > anything servicemix-saxon could offer. > > Cheers, > > Ashwin... > > > raulvk.soa 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-tp20678812p20686328.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
