You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Henry Zongaro (JIRA)" <xa...@xml.apache.org> on 2009/11/26 12:34:39 UTC

[jira] Commented: (XALANJ-2490) Class name derived from namespace URI, not xalan:script element

    [ https://issues.apache.org/jira/browse/XALANJ-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782849#action_12782849 ] 

Henry Zongaro commented on XALANJ-2490:
---------------------------------------

Hi, Martin.
Much of the documentation was originally written with the Xalan-J interpreter in mind.  XSLTC-specific limitations and differences are described on pages that are specific to XSLTC.  In particular, if you check the list at [1] you'll see that XSLTC does not support the xalan:component and xalan:script elements.

Of course, it would be nice if the XSLTC documentation was better integrated into the main Xalan-J documentation, so that differences could be called out in context.

We can either resolve this issue by returning it as "working as designed," or by changing it to an enhancement request.  Which would you prefer?

[1] http://xml.apache.org/xalan-j/extensions_xsltc.html#constraints

> Class name derived from namespace URI, not xalan:script element
> ---------------------------------------------------------------
>
>                 Key: XALANJ-2490
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2490
>             Project: XalanJ2
>          Issue Type: Bug
>      Security Level: No security risk; visible to anyone(Ordinary problems in Xalan projects.  Anybody can view the issue.) 
>          Components: Xalan-extensions
>    Affects Versions: The Latest Development Code
>            Reporter: Martin von Gagern
>
> When implementing extensions in Java, it seems that Xalan (as of SVN revision 752801) uses the namespace url to derive the name of an implementing class, whereas the documentation at http://xml.apache.org/xalan-j/extensions.html#setup-script indicates that the xalan:script subelement of the xalan:component element would be used to bind a namespace to its implementation.
> Before investigating this further, and trying to come up with a fix, I'd like to know which one you consider correct, which one reflects intended behaviour. Do you want to determine class names automagically from its namespace, or do you want to honour the script element when compiling a function call?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org