Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of njuk.njuk@gmail.com
 designates 209.85.223.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=JcCfUkutWeE7rl7xV8XITsi9A/lBX6Zn8+hnG9sEthUEMU+aUEyexb4uB5/hvv+BHI
         tTFfephI3SLn0pOEQKoHhthWJRXJ13+g6GL/7R3lxME0FOK4pij0Nayuu7B8wtso1laq
         TgNcgXv3vsSRk8IuJrjloS5WxLR0v4ghJIGeA=
MIME-Version: 1.0
Date: Mon, 24 Aug 2009 15:10:12 -0700
Message-ID: <573038df0908241510o3d1b3aa3xc80214454fa6a3cc@mail.gmail.com>
Subject: [Digester] re-parsing digest file after modifications yields results
	prior to modification
From: NJuk Njuk <njuk.njuk@gmail.com>
To: user@commons.apache.org
Content-Type: multipart/alternative; boundary=00221532cc80593da50471ea7b95

--00221532cc80593da50471ea7b95
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

i have an application that needs the ability to re-parse the same digest
file multiple times.  each time the digest file will have been modified, so
the resultant object should reflect these modifications.  the digest rules
are defined via xmlrules.  these rules themselves do not change; the
modification is only to the digest file.

assume below digestRulesURL and digestURL are valid URLs (that never change)
pointing to the appropriate files.  each time i setup a new digester
instance and call parse() via the following...

Digester aDigester = DigesterLoader.createDigester(digestRulesURL);
aDigester.setNamespaceAware(true);
aDigester.setXIncludeAware(true);

SomeObject o = (SomeObject) aDigester.parse(digestURL);

...the results of parse() always reflect the first time it was called.  that
is to say, no matter how many times i change the digest file, create a new
digester, and call parse (as above), the resulting object (though seemingly
a new instance) has the same state as the original call to parse().

i know from the Digester FAQ, that one should not reuse a digester object,
which is why i am recreating each time.
there appears to be some sort of caching or state that is maintained.  i
peeked around the xmlrules DigesterLoader code and related, but not enough
to see anything that would tip me off.

any help would be appreciated.

--00221532cc80593da50471ea7b95--