Re: ajax and rundata disposal

Christian Kaiser <[email protected]> Wed, 02 Dec 2009 16:29:46 +0100
Newsgroups gmane.comp.jakarta.turbine.user
Message-ID <1259767786.18068.38.camel@kaiser00c-desktop>
I think I got it now.
Please correct me if I misconceive.
log:

14:51:27,027 [TP-Processor8] DEBUG ...BmsRunData
recycle  ...BmsRunData@1f3bb61
14:51:27,033 [TP-Processor8] DEBUG ...ModelTool   -
refresh  ...BmsRunData@1f3bb61

14:51:27,168 [TP-Processor2] DEBUG ...BmsRunData  -
recycle  ...BmsRunData@3e65be
14:51:27,183 [TP-Processor2] DEBUG ...ModelTool   -
refresh  ...BmsRunData@3e65be
14:51:27,245 [TP-Processor2] DEBUG ...BmsRunData  -
dispose  ...BmsRunData@3e65be

14:51:27,249 [TP-Processor8] ERROR ...ModelTool   - NPE
for  ...BmsRunData@3e65be
14:51:27,256 [TP-Processor8] DEBUG ...BmsRunData  -
dispose  ...BmsRunData@1f3bb61


Processor2 overtakes Processor8.

The modeltool runs in session scope, so only one instance of it exists.
After P8 refreshes the rundata in the tool,
P2 overwrites it with its rundata.
P2 finished and disposed the rundata.
The model tool in P8 has a disposed rundata.


I can prevent from this, when I set the tool in a request scope.
That means the refresh method of the RunDataApplicationTool is not
called, but the Rundata is passed to the Tool with the init method.
The tool gets initialized on every request.

Thats about it for now.
Feel free to add your thoughts.
Thanks for your hints, so far.

Christian