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/06/27 17:17:30 UTC

[jira] Commented: (JCR-367) Remove dependency on Xerces

    [ http://issues.apache.org/jira/browse/JCR-367?page=comments#action_12418041 ] 

Jukka Zitting commented on JCR-367:
-----------------------------------

> Use JAXP Transformer (yes it is part of the Java Runtime siince 1.4) for export

We should be careful with especially namespaces being correctly transmitted through the Transformer interface. There are a few bug reports about the same issue earlier on.

> Copy XMLChar to o.a.j.util. Yes, this is not the best of all solutions, but it removes the dependency and XMLChar is Apache, too.

Agreed. Not nice, but not too bad either.

> Remains the o.a.j.c.nodetype.converter package which contains a XML Schema to node type converter.
> This is probably not a tool, which is run on a casual server implementation. Therefore, leaving the dependency
> there and documenting is probably ok. Better would probably be to take this out fo the core repository package,
> not sure, though.

The XML Schema converter was included in core when I merged the CND support from contrib. It really should be outside the core unless we want to support direct XML Schema imports through registerNodeTypes().

I've also been thinking about replacing the converter with an XSL transformation. Any takers?


> Remove dependency on Xerces
> ---------------------------
>
>          Key: JCR-367
>          URL: http://issues.apache.org/jira/browse/JCR-367
>      Project: Jackrabbit
>         Type: Improvement

>   Components: xml
>     Reporter: Michael Young

>
> Classloaders in certain J2EE servers do not play well with the Xerces requirement

-- 
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

Re: [jira] Commented: (JCR-367) Remove dependency on Xerces

Posted by Felix Meschberger <Fe...@day.com>.

Hi Jukka,

Alright then, so I will then test, my patch and submit it to JIRA on success.

Regards
Felix

On 6/28/06, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On 6/28/06, Felix Meschberger <fm...@gmail.com> wrote:
> > > > Use JAXP Transformer (yes it is part of the Java Runtime siince 1.4) for export
> > >
> > > We should be careful with especially namespaces being correctly transmitted
> > > through the Transformer interface. There are a few bug reports about the same
> > > issue earlier on.
> >
> > Do you have some concrete examples in mind ? Maybe those bugs are less
> > problematic than the Xerces inclusion.
>
> Sorry for not being too specific, I didn't have time to trace proper
> references. See the thread at [1] from a year ago. The problem was
> about StreamSource -> DomResult conversions, where namespace prefixes
> were lost unless the SAX parser's
> "http://xml.org/sax/features/namespace-prefixes" property was set. No
> that I think of it I don't believe that this will be a problem for
> JCR-367, since I think that Xerces is only used directly to serialize
> XML, not to parse it.
>
> [1] http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/1952
>
> BR,
>
> Jukka Zitting
>
> --
> Yukatan - http://yukatan.fi/ - info@yukatan.fi
> Software craftsmanship, JCR consulting, and Java development
>

Re: [jira] Commented: (JCR-367) Remove dependency on Xerces

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On 6/28/06, Felix Meschberger <fm...@gmail.com> wrote:
> > > Use JAXP Transformer (yes it is part of the Java Runtime siince 1.4) for export
> >
> > We should be careful with especially namespaces being correctly transmitted
> > through the Transformer interface. There are a few bug reports about the same
> > issue earlier on.
>
> Do you have some concrete examples in mind ? Maybe those bugs are less
> problematic than the Xerces inclusion.

Sorry for not being too specific, I didn't have time to trace proper
references. See the thread at [1] from a year ago. The problem was
about StreamSource -> DomResult conversions, where namespace prefixes
were lost unless the SAX parser's
"http://xml.org/sax/features/namespace-prefixes" property was set. No
that I think of it I don't believe that this will be a problem for
JCR-367, since I think that Xerces is only used directly to serialize
XML, not to parse it.

[1] http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/1952

BR,

Jukka Zitting

-- 
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development

Re: [jira] Commented: (JCR-367) Remove dependency on Xerces

Posted by Felix Meschberger <fm...@gmail.com>.

Hi Jukka,

Thanks for the comments. I am taking this to the list to not fill JIRA
and will post a summary to JIRA in the end.

> > Use JAXP Transformer (yes it is part of the Java Runtime siince 1.4) for export
>
> We should be careful with especially namespaces being correctly transmitted
> through the Transformer interface. There are a few bug reports about the same
> issue earlier on.

Do you have some concrete examples in mind ? Maybe those bugs are less
problematic than the Xerces inclusion.

Regards
Felix