I would say, this is a bug in Ognl. The problem is in
OgnlRuntime.__getSetMethod(). This method identified with setter to
use base on matching number of parameters (!!!) and sometimes
setId(long) is first and sometimes setId(Object) is on top. I think it
should be rewritten to match on parameter ty
Following a chat with Lukasz on IRC, I post a weird behaviour I got this
morning.
Example:
- QueryAction class with a int selectedParent property
- url on a webpage pointing to:
QueryqueryConversation.action?selectedParent=2
- an action mapping
- Application packaged in .war and deployed in two c
2 matches
Mail list logo