RE: XMLC 2.1 compatibility with JDK 1.3

Thanks for your quick response Richard. I had trouble getting out to the CVS 
repository but I grabbed the 2.2 Alpha 4 that David Li posted. After some 
amount of gyrations with my environment (WSAD 5.0) I was able to get that 
release in and working along with the latest releases of Xerces and Xalan 
(2.3.0 and 2.5.D1 respectively). 

It's good to be free of the Xerces restriction although, unfortunately, it 
hasn't been the panacea that I hoped. I'm trying to track down a memory leak in 
our web app which uses XMLC for page presentation but uses Xerces, Xalan, and 
FOP to produce PDF reports. Since we brought the report generation inside the 
app server we've seen a gradual memory leak that has required a nightly restart 
procedure. Purify has identified the (most) offending leak location to be 
XMLSerializer.endElement(String) although for the life of me I can't figure out 
why. I was hoping the latest release of Xerces would fix the problem -- but no.

I haven't tried out the new document reloading yet but I will real soon.

Anyway, thanks again for your quick response. It was really appreciated. 
Jim

-----Original Message-----
From: Richard Kunze [mailto:kunze@xxxxxxxxx]
Sent: Wednesday, March 12, 2003 8:06 AM
To: xmlc@xxxxxxxxxxx
Subject: Re: Xmlc: 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, kunze@xxxxxxxxx 


Confidentiality Warning:  This e-mail contains information intended only for 
the use of the individual or entity named above.  If the reader of this e-mail 
is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient, any dissemination, publication or 
copying of this e-mail is strictly prohibited. The sender does not accept any 
responsibility for any loss, disruption or damage to your data or computer 
system that may occur while using data contained in, or transmitted with, this 
e-mail.   If you have received this e-mail in error, please immediately notify 
us by return e-mail.  Thank you.