I also did a test that removing the xerces???.jar from xml-xindice/java/lib
directory. It doesn't seem affect the build nor basic query (I didn't test
the RPC staff though).

Is this because I am using j2sdk1.4.1, which already has xerces? If the
problem Kevin mentioned solved, will it still be necessary for Xindice to be
shipped with Xerces???.jar?

Regards,
Lixin

-----Original Message-----
From: Kevin Ross [mailto:[EMAIL PROTECTED]
Sent: Friday, February 14, 2003 11:43 AM
To: [EMAIL PROTECTED]
Subject: RE: Xerces dependency


The dependency I found seems to lie in the XmlRpc.setDriver("xerces")
scattered throughout.

It seems that (http://ws.apache.org/xmlrpc/parser.html) you should be
able to change that easily, by making this configurable (xindice config)
and using the configured implementation in the code.

Just my thoughts from a little perusing...

-Kevin Ross

-----Original Message-----
From: Matt Liotta [mailto:[EMAIL PROTECTED]
Sent: Friday, February 14, 2003 12:27 PM
To: [EMAIL PROTECTED]
Subject: RE: Xerces dependency

I believe I remember seeing comments in the code about the dependency
thus implying to me at least that removal of the dependency would be
non-trivial. However, we have found a business need to remove the Xerces
dependency and figured the project could benefit.

Matt Liotta
President & CEO
Montara Software, Inc.
http://www.montarasoftware.com/
888-408-0900 x901

> -----Original Message-----
> From: Gianugo Rabellino [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 14, 2003 12:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Xerces dependency
>
> Matt Liotta wrote:
> > Actually I wasn't volunteering, but if no one else is working on it
then
> > my company will likely tackle the problem in the coming months. I
just
> > didn't want to waste resources on work someone else was doing.
> >
>
> That would be cool. However, I'm not dead sure that the Xerces
> dependancy can be removed easily from the current codebase. I think
that
> some of the Xindice internals rely on some Xerces code (not exposed by
> Jaxp). This is for sure the case with Xalan, on which the source
relies
> for the XPath compiler (and, BTW, XUpdate too depends on Xalan).
>
> > BTW, any Xindice hackers out there who are looking for contract work
> > implementing changes to Xindice?
>
> Oh well... you have my e-mail, don't you? ;-)
>
> Ciao,
>
> --
> Gianugo Rabellino
> CTO
> Pro-netics s.r.l.
> http://www.pro-netics.com

Reply via email to