History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: COO-162
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Pete Butland
Reporter: Pavi De Alwis
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Google issue summary
Cooee

Provide callbacks for Application Instance thread activation and disposing

Created: 04/Jul/08 03:37 PM   Updated: 14/Jul/08 11:20 AM
Component/s: None
Affects Version/s: COOEE-CORE-1.1
Fix Version/s: COOEE-CORE-1.2


 Description  « Hide
It would be useful for application developers to get events when the Application instance binds to a thread (i.e. activates) and also when it's disposed. In particular this allows applications to manage their own thread local storage handling and be sensitive to thread swapping during a single HTTTP session. For example when implementing strategies for managing PersistentContexts and Conversations.

Also so see related discussions at http://echo.nextapp.com/site/node/3584



 All   Comments   Change History      Sort Order:
Pavi De Alwis - [04/Jul/08 03:47 PM ]
ApplicationInstance generates two java.beans.PropertyChangeEvent notifications.
  • On thread swapping it generates a THREAD_CHANGED_PROPERTY.
  • On the application being disposed it generates a APPLICATION_DISPOSED_PROPERTY.

Daniel Murley - [07/Jul/08 01:11 PM ]
This fix has broken the build.

Pete Butland - [14/Jul/08 11:20 AM ]
The build has been fixed.

Also the APPLICATION_DISPOSED_PROPERTY property has been removed as ApplicationInstance.dispose can be overridden to achieve the same effect.