You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by "raulvk.soa" <ra...@gmail.com> on 2008/11/25 11:44:58 UTC
Reloadable XSLT in servicemix-saxon
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.
Re: Reloadable XSLT in servicemix-saxon
Posted by "raulvk.soa" <ra...@gmail.com>.
Done. https://issues.apache.org/activemq/browse/SM-1704.
gnodet wrote:
>
> That makes sense. Please raise a JIRA for this improvement.
>
> On Tue, Nov 25, 2008 at 11:44 AM, raulvk.soa <ra...@gmail.com> 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
>
>
--
View this message in context: http://www.nabble.com/Reloadable-XSLT-in-servicemix-saxon-tp20678812p20686596.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Reloadable XSLT in servicemix-saxon
Posted by Jon Brisbin <jo...@jbrisbin.com>.
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 <ra...@gmail.com>
> 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
Re: Reloadable XSLT in servicemix-saxon
Posted by "raulvk.soa" <ra...@gmail.com>.
Jeff,
Many thanks! Your solution works wonderfully ;)
Jeff Peterson-3 wrote:
>
> 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 <gn...@gmail.com> wrote:
>> That makes sense. Please raise a JIRA for this improvement.
>>
>> On Tue, Nov 25, 2008 at 11:44 AM, raulvk.soa <ra...@gmail.com>
>> 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
>>
>
>
--
View this message in context: http://www.nabble.com/Reloadable-XSLT-in-servicemix-saxon-tp20678812p20686386.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Reloadable XSLT in servicemix-saxon
Posted by Jeff Peterson <j....@gmail.com>.
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 <gn...@gmail.com> wrote:
> That makes sense. Please raise a JIRA for this improvement.
>
> On Tue, Nov 25, 2008 at 11:44 AM, raulvk.soa <ra...@gmail.com> 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
>
Re: Reloadable XSLT in servicemix-saxon
Posted by Guillaume Nodet <gn...@gmail.com>.
That makes sense. Please raise a JIRA for this improvement.
On Tue, Nov 25, 2008 at 11:44 AM, raulvk.soa <ra...@gmail.com> 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
Re: Reloadable XSLT in servicemix-saxon
Posted by "raulvk.soa" <ra...@gmail.com>.
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.
Re: Reloadable XSLT in servicemix-saxon
Posted by Ashwin Karpe <as...@progress.com>.
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.
>
>
>
-----
---
Ashwin Karpe, Principal Consultant, PS - Opensource Center of Competence
Progress Software Corporation
14 Oak Park Drive
Bedford, MA 01730
---
+1-972-304-9084 (Office)
+1-972-971-1700 (Mobile)
----
Blog: http://opensourceknowledge.blogspot.com/
--
View this message in context: http://www.nabble.com/Reloadable-XSLT-in-servicemix-saxon-tp20678812p20680347.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.