Re: XMLC 2.1 compatibility with JDK 1.3

On Wednesday 12 March 2003 14:27, Cakalic, James wrote:
> Hi, all. I'm currently using a version of XMLC somewhere between 2.0.1 and
> 2.1 that was "lifted" from the Enhydra Application Server release 4.1. It's
> been working fine but, because of external drivers, I'm trying to migrate
> to the real 2.1 release.
>
> Here's my question: Is it possible that the XMLC 2.1 release was compiled
> using JDK 1.4? I ask because I'm getting in some circumstances -- not
> directly related to XMLC but using the xerces XMLSerializer -- I'm getting

I don't recall the details (it's been a while since I compiled and released 
XMLC 2.1 :-) but it's quite possible that I did compile with 1.4. The error 
you're getting certainly indicates that I did...

Now, XMLC doesn't use any 1.4 specific features and compiles with JDK 1.3 
without any problems. If you can access CVS repositories, I'd recommend that 
you check out the latest sources from XMLC's anonymous CVS (Instructions are 
at http://debian-sf.objectweb.org/cvs/?group_id=49) and compile it yourself. 
The build is pretty much self-contained, the only external dependencies are a 
JDK and ant. 

By using the latest CVS, you get some additional benefits over the 2.1 
version, namely
- On-the-fly document reloading
- XMLC coexists with newer Xerces versions

Hope this helps,

Richard

-- 
Richard Kunze 

[ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
http://www.tivano.de, [email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+bz6986Aqb3OZfF4RAnd0AJ0SZEFX5zT434z4bH3vi1T675xVQACfTwjX
46IqayI3F30sdFvVSEZJX48=
=HDqo
-----END PGP SIGNATURE-----