[ http://mc4j.org/jira/browse/STS-225?page=all ]
Tim Fennell resolved STS-225.
-----------------------------
Resolution: Fixed
Now that I've got the new binding implementation working this is a pretty easy
fix! The binder now has a new method:
isBindingAllowed(PropertyExpressionEvaluation eval)
The default implementation of this method looks as the first node in the
evaluation, and if it is of type ActionBeanContext (or a subclass thereof)
binding is veto'd.
> All request properties with names starting with 'context' are ignored during
> binding
> ------------------------------------------------------------------------------------
>
> Key: STS-225
> URL: http://mc4j.org/jira/browse/STS-225
> Project: Stripes
> Issue Type: Bug
> Components: ActionBean Dispatching
> Affects Versions: Release 1.3.2
> Reporter: Akbar Ibrahim
> Assigned To: Tim Fennell
> Priority: Minor
> Fix For: Release 1.4
>
>
> Request properpties with names starting with 'context', for example
> 'contextId', are never bound to the action bean. The reason seems to be this
> if condition in the OgnlActionBeanPropertyBinder.bind method
> !pname.toLowerCase().startsWith("context")
> Need a <quote>equally bullet proof yet higher fidelity</quote> replacement
> for this check. :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mc4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
