RE: Fwd: Xmlc: New location for XMLC Alpha download. ..
Kirk Daries <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <D09B591872D1D611AF2B0010B5A1AAD0433CDB@WCSMAIL> |
Great Stuff!! Whoopee! :D -----Original Message----- From: Richard Kunze [mailto:[email protected]] Sent: 11 March 2003 01:28 To: [email protected] Subject: Re: [Barracuda] Fwd: Xmlc: New location for XMLC Alpha download. .. On Tuesday 11 March 2003 10:10, Kirk Daries wrote: > Hi Jake, > > Apologies for sounding ignorent.. but.. > What exactly do you mean by "deferred parsing for runtime document > reloading"? The document isn't compiled into the XMLC class anymore, but gets parsed at first access and whenever a change to the source file is detected. The XMLC class simply provides the interface to the document (i.e. access methods and so on) > Does this mean, tomcat can recycle references to the XMLC doc's so we can > get around the issue of having to stop-start Tomcat in version 3.3 of > Tomcat? Depends. The contents of the document can change arbitrarily and the changes are picked up by the reloading code. The XMLC class however can't change (due to the fact that it's impossible in Java to recycle class definitions at will). This means that if e.g. the compiled class has an access method "getTagFoo()" but the reparsed version of the document does not define an id named "foo" then getTagFoo() will still exist, but return null. And if the reparsed document defines a new id "bar", XMLC cannot generate a "getTagBar()" method on the fly (that's planned for the next major version, but I'm not sure how to implement it best yet). If you use XMLC only as a DOM factory (like Barracuda does), then yes, you can exchange the document contents on-the-fly, without any classloader hassles. :-) 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]