RE: Enhydra 3.1 and Xerces 1.3.1

Thanks for the reply.  Unfortunately we have not decided to move to
Enhydra 5.0, so I need to consider my options with Enhydra 3.1.

I tried posting a message on the XMLC mailing list.

-tom

> -----Original Message-----
> From: enhydra-admin@xxxxxxxxxxx [mailto:enhydra-admin@xxxxxxxxxxx] On
> Behalf Of Mike Warne
> Sent: Thursday, November 07, 2002 12:50 PM
> To: enhydra@xxxxxxxxxxx
> Subject: RE: Enhydra: Enhydra 3.1 and Xerces 1.3.1
> 
> Hi Tom,
> 
> Enhydra 5.0 uses xerces 1.4.4.  I'm not sure, but this may possibly
allow
> FOP to work.  I am using 5.0 with iText (JasperReports) and can
produce
> PDF files without problems. I've never worked with FOP though.
> 
> The xerces patches are related to XMLC.  Try posting to the xmlc group
for
> more information.  There is also  new push to refactor xmlc to use
xerces
> 2.
> 
> Xerces is a problem for many apps and app servers.  Even without any
> patching xerces appears to break compatiblity from one release to the
> next. It's not just a problem for Enhydra, but also Tomcat, Weblogic
and
> probably others. I think an implementation of the DOM api is now even
> built into jdk1.4. It seems to me, that the api keeps changing and is
not
> very backward compatible.
> 
> Mike.
> 
> 
> -----Original Message-----
> From: Tom Gates [mailto:tgates@xxxxxxxxxxx]
> Sent: Thursday, November 07, 2002 6:09 AM
> To: enhydra@xxxxxxxxxxx
> Subject: Enhydra: Enhydra 3.1 and Xerces 1.3.1
> 
> 
> I have an Enhydra 3.1 application that that is using FOP.  The version
> of FOP that I am using is dependent on Xerces-J 1.3.1.  Enhydra 3.1
also
> has its own built-in copy Xerces-J, but that version is a customized
> version of Xerces-J 1.2.0.  Xerces-J 1.3.1 does not contain any of the
> Enhydra specific customizations.
> 
> Question 1: How can I work around the Xerces version problem?  I
> downloaded sources for Xerces-J 1.2.0 and Xerces-J 1.3.1 and did a
> three-way analysis of the changes made in each version.   There were a
> significant number of differences between 1.2.0 and 1.3.1 such that it
> will be very hard to patch in the Enhydra specific changes?
> 
> Question 2: Xerces seems like a popular package that is used by
several
> other tools and technologies.  What did the Enhdyra developers choose
to
> make a customized version of Xerces?   Doing so makes it hard for
> developers to mix Enhydra with other 3rd-party tools and technologies
> that also use Xerces.
> 
> -tom
> 
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra
> 
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra