servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SM-1705) Make Resources in ServiceMix-Saxon smart enough to reload themselves
Date Mon, 01 Dec 2008 13:34:05 GMT

     [ https://issues.apache.org/activemq/browse/SM-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Nodet resolved SM-1705.
---------------------------------

       Resolution: Fixed
    Fix Version/s: servicemix-saxon-2008.02
         Assignee: Guillaume Nodet

Thanks a lot for this patch.

Sending        trunk/src/main/java/org/apache/servicemix/saxon/SaxonEndpoint.java
Sending        trunk/src/main/java/org/apache/servicemix/saxon/XQueryEndpoint.java
Sending        trunk/src/main/java/org/apache/servicemix/saxon/XsltEndpoint.java
Sending        trunk/src/main/java/org/apache/servicemix/saxon/XsltProxyEndpoint.java
Sending        trunk/src/test/resources/spring.xml
Transmitting file data .....
Committed revision 722067.

> Make Resources in ServiceMix-Saxon smart enough to reload themselves
> --------------------------------------------------------------------
>
>                 Key: SM-1705
>                 URL: https://issues.apache.org/activemq/browse/SM-1705
>             Project: ServiceMix
>          Issue Type: New Feature
>          Components: servicemix-saxon
>    Affects Versions: servicemix-saxon-2008.01
>            Reporter: Jon Brisbin
>            Assignee: Guillaume Nodet
>            Priority: Minor
>             Fix For: servicemix-saxon-2008.02
>
>         Attachments: always_reload.diff.txt
>
>
> It would be nice if the XSLT and XQuery resources inside the Saxon SE could monitor themselves
for modifications and reload the Source when that event happens. This would work easily for
file:/// resources (and classpath: for that matter, since Spring IO gives you the modification
time of the jar file in which the resource lives), but other protocols would have to be fetched
and hashed to tell if they've changed or not.
> I've implemented a simple patch against trunk that allows you to add a "reload" attribute
to the saxon:xslt element that tells it to always reload the resource. This isn't ideal, but
will work for all URL types that Resource handles. Anything more smart would have to be multi-threaded,
like a File watcher.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message