[
https://jira.codehaus.org/browse/JBEHAVE-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284099#comment-284099
]
Diego Rivera commented on JBEHAVE-646:
--------------------------------------
Understood - I guess this was a simple case of RTFM :)
However, would this behavior be desirable? I.e. using "named" to
supersede/supplant the ordering? It seems natural that if one chooses for
parameters to be named, and uses @Named() to enforce it, that JBehave would
respect that even in a non-parameterized scenario.
> @Named not respecting parameter order
> -------------------------------------
>
> Key: JBEHAVE-646
> URL: https://jira.codehaus.org/browse/JBEHAVE-646
> Project: JBehave
> Issue Type: Bug
> Reporter: Diego Rivera
>
> @Named doesn't seem to do its job, and parameter ordering in the method
> declaration seems to confuse the assignment code. For instance:
> "Given a $var1 with $var2 and $var3"
> void testVars(@Named("var3") String var3, @Named("var1") String var1,
> @Named("var2") String var2)
> When executing testVars, it assigns var3=$var3, var1=$var1, but var2=$var3
> Clearly, the correct assignment is var2=$var2
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
