DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29760>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29760 extension-element-prefixes and imported stylesheets Summary: extension-element-prefixes and imported stylesheets Product: XalanJ2 Version: 2.5Dx Platform: All OS/Version: Other Status: NEW Severity: Major Priority: Other Component: org.apache.xalan AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, On a large Web site based on Xalan for all dynamic renditions, our situation is the following: - we have reusable stylesheet fragments imported in many transformations (using xsl:import) - we are using our own Java extensions for efficientely performing some frequent tasks (like transformation of EDI codes to labels, and so one) Our problem is that it is not enough to define "extension-element-prefixes" on the xsl:styleshete of imported XSL fragments: the Xalan "extension-element- prefixes" must be defined as well on the root stylesheet element. This is a issue for quality-control of developments because the developpers of new stylesheet must look in all nested imports in order to figure out whether which "extension-element-prefixes" is needed on his own main stylesheet file. Moreover, when improdinv reusable fragments and adding new extensions, we have to look for all stylesheets importing the fragment in order to add "extension- element-prefixes". This doesn't sound normal at all to me. Would you agree to recognize this a s a bug? PS this issue is actually there since Xalan Java v1 already. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
