[
https://issues.apache.org/struts/browse/WW-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes Wannemacher closed WW-2534.
-------------------------------
Resolution: Won't Fix
I agree with Dave, the method chaining pattern commonly used like in JQuery
doesn't fit in well with simple JavaBeans. I'm closing this for now since no
one else has weighed in with a good way to approach it. A patch would be
welcome, but I think adding support for this would require quite a bit of
refactoring.
> Parameters interceptor does not understand method chaining
> -----------------------------------------------------------
>
> Key: WW-2534
> URL: https://issues.apache.org/struts/browse/WW-2534
> Project: Struts 2
> Issue Type: Improvement
> Components: Core Interceptors
> Affects Versions: 2.0.11
> Reporter: Johnny Wey
> Priority: Minor
> Fix For: Future
>
>
> While using method chaining (see
> http://martinfowler.com/dslwip/MethodChaining.html) for our domain objects,
> we noticed that Struts doesn't seem to understand the object's return
> reference for automatic object population from the page's form parameters.
> We get the following message when trying to set parameters in this domain
> objects:
> ERROR ParametersInterceptor.setParameters()204 - ParametersInterceptor -
> [setParameters]: Unexpected Exception caught setting '[domainProperty]' on
> 'class [our action]': Error setting expression '[ourExpression]' with value
> '[Ljava.lang.String;@81b051'
> (The items in [ ] I have replaced with generic descriptions of the specific
> values)
> Removing the returned reference value fixes the problem, and the interceptor
> runs as advertised.
> Thanks!
> Johnny Wey
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
