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

Key: XW-522
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: tm_jee
Reporter: tm_jee
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
XWork

Interceptor destroy() method is never called.

Created: 27/May/07 01:24 PM   Updated: 02/Jun/07 04:02 AM
Component/s: Interceptors
Affects Version/s: 1.1.3
Fix Version/s: 1.2.3


 Description  « Hide
Interceptor's destroy method is never called.

One possible way to fix this would be to :-

* When FilterDispatcher destroy itself (its destroy() method)
* It calls DispatcherUtil's cleanup() method
* which could call ConfigurationManager.destroyConfiguration()
* we could add the code to destroy the interceptor there.

The idea is to get the RuntimeConfiguration, and then get the actionConfigs which is
Map<String, Map<String, ActionConfig>>
The first String is the namespace, while the second String is the action name, With ActionConfig we could get a list of ActionMapping which holds an instance of Interceptor object. We could then invoke destroy() method on it.

thoughts?

 All   Comments   Change History      Sort Order:
tm_jee - [02/Jun/07 04:02 AM ]
fixed. Kindly review.

Changes at:-
tmjee@tmjee-laptop:~/development/xwork_1-2/src$ svn commit test/com/opensymphony/xwork/config/ConfigurationManagerTest.java java/com/opensymphony/xwork/XWorkTestCase.java java/com/opensymphony/xwork/config/ConfigurationManager.java
Sending java/com/opensymphony/xwork/XWorkTestCase.java
Sending java/com/opensymphony/xwork/config/ConfigurationManager.java
Sending test/com/opensymphony/xwork/config/ConfigurationManagerTest.java
Transmitting file data ...
Committed revision 1533.