You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2006/10/25 12:16:17 UTC
[jira] Updated: (JCR-602) importXML still depends on Xerces
[ http://issues.apache.org/jira/browse/JCR-602?page=all ]
Jukka Zitting updated JCR-602:
------------------------------
Component/s: JCR TCK
> 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