[ http://mc4j.org/jira/browse/STS-156?page=all ]
Ben Gunter closed STS-156.
--------------------------
Fix Version/s: Release 1.5
Resolution: Fixed
Assignee: Ben Gunter (was: Tim Fennell)
This is accomplished by the @StrictBinding annotation.
> Allow intentional @In, @Out, @NoBinding annotations on ActionBean
> variables/properties
> --------------------------------------------------------------------------------------
>
> Key: STS-156
> URL: http://mc4j.org/jira/browse/STS-156
> Project: Stripes
> Issue Type: New Feature
> Components: Validation
> Reporter: Jeppe Cramon
> Assigned To: Ben Gunter
> Fix For: Release 1.5
>
>
> Text changed slightly from stripes-users thread about this issue:
> Allowing users to use @NoBinding, @In and @Out to ActionBean
> properties/variables would be good, as long as the default is that if nothing
> is specified then it's both @In and @Out.
> @Out is cool for when you provide pure output data (like a view). It doesn't
> really make sense to perform binding on it. It also makes the intent of
> variables more clear IMO.
> For larger ActionBeans (often large because they have 2-3 event handlers) it
> starts to get messy, because some properties/variables are for Spring
> binding, some are output data, some are pure input data and then some are
> both ways.
> For Spring bindings are want to be absolutely sure that no binding can occur.
> Worst case is a configurable service which have setters/getters for
> configuration, that normally only is accessed during application
> initialization, but now suddenly gets overridden by accident or by bad
> intent, however this is not likely to happen.
> For a readonly view bean I actually would like to state to Stripes that it
> shouldn't try to bind data back. If data is submitted that would have
> resulted in databinding, but the property/variable is strictly @Out, then
> Stripes to flag that as an info, etc. It might be a mistake that data gets
> submitted back or it might be a mistake that it was only @Out.
> What I like about @In,@Out,@NoBinding is that they can be used to show the
> intent of the variables/properties. Kind of documentation which also serves a
> purpose (like catching binding to properties you never intended to bind to)
> :-)
> /Jeppe
--
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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
