[
https://issues.apache.org/struts/browse/WW-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43459#action_43459
]
Dave Newton commented on WW-2534:
---------------------------------
Method chaining doesn't follow the JavaBean spec; the expectation is that
properties will follow the JavaBean convention.
I'm not closing this issue as another committer may want to add more, but this
isn't a bug, it's expected behavior.
> Parameters interceptor does not understand method chaining
> -----------------------------------------------------------
>
> Key: WW-2534
> URL: https://issues.apache.org/struts/browse/WW-2534
> Project: Struts 2
> Issue Type: Bug
> Components: Core Interceptors
> Affects Versions: 2.0.11
> Reporter: Johnny Wey
> Priority: Minor
>
> 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.
