[ http://issues.apache.org/jira/browse/XALANJ-1897?page=all ]
Brian Minchau updated XALANJ-1897:
----------------------------------
Fix Version: 2.7
> extension-element-prefixes and imported stylesheets
> ---------------------------------------------------
>
> Key: XALANJ-1897
> URL: http://issues.apache.org/jira/browse/XALANJ-1897
> Project: XalanJ2
> Type: Bug
> Components: Xalan-extensions
> Versions: 2.5Dx
> Environment: Operating System: Other
> Platform: All
> Reporter: Philippe Vijghen
> Assignee: Xalan Developers Mailing List
> Fix For: 2.7
>
> 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.
--
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]
