David Jencks wrote:
Go for it.
IMO the stop should exactly undo what start does. No other cleanup should be necessary.
I agree - but JSR77 does not.
stop() will have to undo exactly what startRecursive() does. There is no inverse of start().
I would have preferred if jsr77 had a stopRecursive() but no stop()
Note that the patch did not actually do this. I made the start method lazily create fields that were stop does not free. The contents of the destroy() methods will need to be moved to the doStop() methods.
I'll try to do this in the next day or two (unless a destroy defender steps forward). But if you want to do this yourself... feel free to take this over for now.
cheers
-- Greg Wilkins<[EMAIL PROTECTED]> Phone/fax: +44 7092063462 Mort Bay Consulting Australia and UK. http://www.mortbay.com
