On 11/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 11/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On 11/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > > > On 11/13/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > > > > > On 11/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > > > On 11/13/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > > <snip/> > > > > > > > > > > OK, can't seem to reproduce this locally (even without the JCL and > > > > > BeanUtils cleanup, since the dialog-scxml module doesn't yet have > > > > > that). I'm on: > > > > > > > > > > XP SP2 > > > > > Tomcat 5.0.28 (using manager to undeploy) > > > > > > > > > > > > I'm on XP SP2 as well, using Tomcat 5.5.17 and using manager to > > > undeploy. > > > > The symptoms I get is that everything gets deleted out of the > > > webapps/xxxxx > > > > directory except WEB-INF/lib/shale-dialog-basic-xxx.jar, so the > > > directory > > > > itself cannot be deleted. > > > > > > > > I'm going to try 5.0.x as well as a more recent version of 5.5 to see > > > if the > > > > behavior changes for me. > > > > > > > <snap/> > > > > > > I got 5.5.17 and got shale-dialog-basic-1.0.4-SNAPSHOT.jar to lock on > > > undeploy as you had indicated previously. The dialog-scxml test app > > > undeployed successfully. > > > > > > Can you please try shale-test-dialog-scxml ? > > > > > > Interesting ... that works under 5.5.20, while the dialog-basic test app > > fails (as it did before I started changing anything about the cleanup). Now > > to figure out what we're doing differently ... > > > > AHA ... just figured out what we are doing differently. The > shale-dialog-basic library registers two resources (embedded in the jar > file) for the 1.0 and 1.1 DTDs of a dialog configuration resource. The > shale-dialog-scxml library does not (currently) have such a thing. If I > comment out the registrations (temporarily forcing Digester to go out to the > Internet to resolve them), I can undeploy successfully on 5.5.20. > > Now, we need to figure out how to get Digester to release registered > resources. Looks like it might be related to this bug: http://issues.apache.org/jira/browse/DIGESTER-29 Seems that the patch was applied, so might be worth dropping in a Digester Nightly Build and seeing if that resolves it: http://people.apache.org/builds/jakarta-commons/nightly/commons-digester/
Thanks Niall ... that was it exactly! The problem still exists with Digester 1.7, but is fixed with the latest nightly build of DIgester. Niall Craig
-Rahul > > > > > Craig
