Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: domain of igornaumov@hotmail.com
 designates 65.54.246.214 as permitted sender)
Message-ID: <BAY103-F14536C4BAF33626C6CC5BAD2630@phx.gbl>
From: "Igor Naumov" <igornaumov@hotmail.com>
To: dev@cocoon.apache.org
Subject: web3 block - lifecycle issues and class design
Date: Fri, 30 Mar 2007 13:36:39 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

I have been using the block web3 for some time and ran into a couple of 
issues.

Most of them are related to the lifecycle of the class - it seems that some 
things are preventing a clean instantiation/disposal of the block classes.

In particular, method Web3DataSourceSelectorImpl.dispose() destroys (through 
=null ) the manager and lock properties. For some reason when an application 
(Cocoon) is restarted (without restarting servlet/J2EE/JVM, e.g. through a 
URL ?cocoon-reload=true), the class (Web3DataSourceSelectorImpl) is not 
completely unloaded, so the private static properties are not 
re-initialized.
That causes a null pointer exception next time the class is used.

So may be the code needs to be changed to init the static properties if they 
are null, or remove the lines that set them to null in the dispose() method.

As a workaround, can anybody suggest a way to "unload" the class? (e.g. when 
restarting Cocoon, or even without it)

_________________________________________________________________
Live Search Maps � find all the local information you need, right when you 
need it. http://maps.live.com/?icid=hmtag2&FORM=MGAC01