jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-602) importXML still depends on Xerces
Date Wed, 25 Oct 2006 10:16:17 GMT
     [ http://issues.apache.org/jira/browse/JCR-602?page=all ]

Jukka Zitting updated JCR-602:

    Attachment: XercesTestCases.patch

Attached a patch that removes the Xerces dependency from the mentioned test cases.

Note that I also replaced a number of long throws clauses with a simple "throws Exception"
to avoid adding another exception (ParserConfigurationException) to the list. This shouldn't
be a problem since the only recipient of the exceptions is the unit test framework  that doesn't
really care about the type of the exception.

I'm a bit worried about making direct changes to the TCK codebase, so could someone who's
more involved with the TCK quickly review the patch before I commit it? I don't see any problems
as the change should have no functional effects, I just want to make sure I don't accidentally
mess with something important.

> importXML still depends on Xerces
> ---------------------------------
>                 Key: JCR-602
>                 URL: http://issues.apache.org/jira/browse/JCR-602
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: xml, JCR TCK
>    Affects Versions: 1.1
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.1.1
>         Attachments: XercesTestCases.patch
> Przemo Pakulski commented on JCR-367:
> > Jackrabbit-core is still dependent on Xerces directly during runtime, SessionImpl.importWorkspace,
> > Workspacempl.importWorkspace methods contains folliwng lines :
> >
> >             XMLReader parser =
> >                     XMLReaderFactory.createXMLReader("org.apache.xerces.parsers.SAXParser");
> >
> > It works in maven1 probably because maven1 itself needs xerces to run test goal.
> >
> > I suggest reopening the issue.
> Creating a new issue since JCR-367 is already closed after the 1.1 release.

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


View raw message