jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ragy Eleish (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-217) class org.apache.jackrabbit.name.QName has a hardcoded dependency on Xerces
Date Fri, 16 Sep 2005 13:42:55 GMT
    [ http://issues.apache.org/jira/browse/JCR-217?page=comments#action_12329542 ] 

Ragy Eleish commented on JCR-217:

 I don't think there is a licensing issue with a dependency on JAXP, it is a JDK API. For
example Xerces and Xalan implements on JAXP, while Tomcat depens on it to pick the parser.

Having a dependency on Xerces limit what your users can do, and it is pretty trivial to fix.
Just use JAXP to pick up the XSLTTransformer the same way Tomcat does, and take the implementation
of the of helper functions in your code.

We will do the fix and uploaded to this bug description.

> class org.apache.jackrabbit.name.QName has a hardcoded dependency on Xerces
> ---------------------------------------------------------------------------
>          Key: JCR-217
>          URL: http://issues.apache.org/jira/browse/JCR-217
>      Project: Jackrabbit
>         Type: Improvement
>     Versions: 1.0
>     Reporter: Ragy Eleish
>     Priority: Minor

> The class org.apache.jackrabbit.name.QName, has an unneeded dependency on Xerces which
make it difficult to work with the XML parser or ones choice.
> The dependency (on line 246) is on the method "XMLChar.isValidNCName" only. I suggest
one of the following solutions
> - Copy the implementation of this method to the QName class, it is a very simple implementation.
> - Use the mehtod provided in JAXP 1.3 javax.xml.XMLUtils.isValidNCName, which will create
dependency on JAXP 1.3 though. JDK 1.5 ships with JAXP 1.3
> This dependency is causing us alot of trouble since we need to use another parser that
is optimized for large XML data. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message