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

Key: WW-1475
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: tm_jee
Reporter: Onyeje Bose
Votes: 0
Watchers: 0
Operations

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

ChainingInterceptor does not properly parse the incoming included or excluded methods

Created: 30/Aug/07 09:23 PM   Updated: 30/Nov/07 08:33 AM
Component/s: Interceptors
Affects Version/s: 2.2.6
Fix Version/s: 2.2.7


 Description  « Hide
The ChainingInterceptor does not properly parse the incoming included or excluded methods.
If passed in values, via <param name="includedMethod">foo,bar</param>, the interceptor ends up with a collection of one string "foo.bar".

For example the ValidationInterceptor, a subclass of MethodFilterInterceptor, uses the TextParseUtil.commaDelimitedStringToXXX to properly parse the param. I believe this is the same behavior ChainingInterceptor should exhibit.

 All   Comments   Change History      Sort Order:
tm_jee - [30/Nov/07 08:32 AM ]
Fixed. Kindly review. changes are :-

Sending java/com/opensymphony/xwork/interceptor/ChainingInterceptor.java
Sending test/com/opensymphony/xwork/interceptor/ChainingInterceptorTest.java
Adding test/com/opensymphony/xwork/util/MyListObject.java
Sending test/com/opensymphony/xwork/util/OgnlUtilTest.java
Transmitting file data ......
Committed revision 1695.

Thanks Onyeje