I thought that the problem was, how to handle the change not
how to recognize it.
If the xsl is just file and you know where it is,
what about this:
long mLastLoad = 0;
File mXSLFile = new File(<path-to-file>);
if (mXSLFile.lastModified() > mLastLoad) {
doWhatEverToReRead();
mLastLoad = (new Date()).getTime();
}
P.S.:
I still beg that the real problem lies in doWhatEverToReRead()
> -----Urspr�ngliche Nachricht-----
> Von: Lauer, Oliver [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 28. Februar 2002 18:01
> An: 'Tomcat Users List'
> Betreff: AW: XSL - Reload a resource without restarting
> I'm going to try it. Thanks !
>
> -----Urspr�ngliche Nachricht-----
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 28. Februar 2002 17:51
> An: Tomcat Users List
> Betreff: Re: XSL - Reload a resource without restarting
<snip/>
> If you do a getResource from the ServletContext, it will give you a
> java.net.URL. Then, maybe you could do an openConnection on
> the URL to get a URLConnection. Then, try the getLastModified method
on
> that... Don't know if this will work, but figured I'd throw it out
there
> as a suggestion.
<snip/>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
