DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10244>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10244 XSLTProcessorImpl.resolve() may deliver null Source to Transformer Summary: XSLTProcessorImpl.resolve() may deliver null Source to Transformer Product: Cocoon 2 Version: 2.0.3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If a ressource referenced from inside a XSL stlye sheet by a xsl:include, xsl:import or document() cannot be resolved or is not found, a null Source may be returned to the Transformer, which may lead to problems during transformation and weird log messages. Saxon 6.5 falls back to its own resolver in this case, which can result in irritating "Malformed URL" or "URL not found" messages. It is suggested to always throw a TransformerException if something goes wrong. At least the condition should be logged, currently there is absolutely no hint that for example a ressource was not found, which makes even simple misspellings hard to track down. Unfortunately, an XSLT processor can choose whether it recovers from an exception in the resolver or whether stylesheet compilation resp. the transformation is aborted. I suspect either writing a Xalan respective Saxon-specific transformer component or a more generic TraxTransformer is necessary in order to deal with processor specific configuration settings. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
