[
http://issues.apache.org/jira/browse/XALANJ-1650?page=comments#action_12358696
]
Robert den Uijl commented on XALANJ-1650:
-----------------------------------------
Actually, comparing the timestamp of the compiled stylesheet and it's source
will only take place in case of local files, see related code-snippet:
private String getStylesheetFileName(Source source)
{
String systemId = source.getSystemId();
if (systemId != null) {
File file = new File(systemId);
if (file.exists())
return systemId;
else {
URL url = null;
try {
url = new URL(systemId);
}
catch (MalformedURLException e) {
return null;
}
if ("file".equals(url.getProtocol()))
return url.getFile();
else
return null;
}
}
else
return null;
}
Remote files simply are ignored!
Tested running Xalan 2.6.0 on WebSphere Application Server, on AIX and on
Windows XP.
> TransformerFactory ignores attribute: "auto-translet" and "use-classpath"
> causes an exception
> ---------------------------------------------------------------------------------------------
>
> Key: XALANJ-1650
> URL: http://issues.apache.org/jira/browse/XALANJ-1650
> Project: XalanJ2
> Type: Bug
> Components: JAXP
> Versions: 2.5Dx
> Environment: Operating System: Windows NT/2K
> Platform: Other
> Reporter: Daniel Pfeifer
> Assignee: Xalan Developers Mailing List
>
> The XSLTC documentation states that the attribute auto-translet creates a new
> translet class if the XSL timestamp has changed. This is unfortunately not
> the
> case. The attribute is ignored and the translet does not reflect the changes
> in
> the XSL file. The InvalidAttributeException is not thrown.
> TransformerFactory tf = TransformerFactory.newInstance();
> tf.setAttribute("translet-name", className);
> tf.setAttribute("destination-directory", transletPath);
> tf.setAttribute("package-name", "org.danielp.beta.infolist.translet");
> tf.setAttribute("generate-translet", Boolean.TRUE);
> //tf.setAttribute("use-classpath", Boolean.TRUE);
> tf.setAttribute("auto-translet", Boolean.TRUE);
> Additionally the use-classpath attribute throws an exception if used if the
> translet does not exists. The documentation does not give the impression that
> this behaviour is to be expected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
