
| Key: |
WW-1475
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
tm_jee
|
| Reporter: |
Onyeje Bose
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
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.
|
|
Description
|
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. |
Show » |
|
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