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: [email protected]
For additional commands, e-mail: [email protected]
