> Hi,I could not find anything wrong with > auto-translet using Xalan 2.7.0. The only thing that seems to cause > it to misbehave is if the time on the two systems is out of sync. Could > you give more details as to what is going wrong (e.g. you changed the source > but it doesn't recompile), and how you have the two systems set up (how > does the first system access the source on the second system)?Thanks. > Erin Harris
Hi, We're using Xalan 2.6.0. However, in 2.7.0 the getStylesheetFileName method has not been changed. Description of runtime setup and noticed behavior: - stylesheet is on a remote server (http://myhost/apath/named.xsl) - runtime this URL is set via setSystemId (source.setSystemId(xslUri.toExternalForm());) - if not yet compiled, compilation will take place - if compiled, internally in xsltc getBytecodesFromClasses will be called - remote stylesheet has been changed after compilation took place - to exclude caching issues, server has been stopped and started - to exclude out of sync timestamp issues several tests have been run several days after compilation took place (timestamps have been verified manually also) - once compiled, with the current settings, using auto-translet combined with http-protocol, as long as the class files remain in the destination directory there's no way the remote stylesheet will ever be recompiled again - crucial in this scenario is the getStylesheetFileName method: * File file = new File(systemId); --> non existing File object * ("file".equals(url.getProtocol())) --> nope, getProtocol() returns 'http' * as a fix URLConnection should be used? - tests have been run in debug and non-debug mode; in debug mode we noticed the behavior regarding the getStylesheetFileName method I hope this clarifies the issue. Regards, Robert
