[
https://jira.codehaus.org/browse/JBEHAVE-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284080#comment-284080
]
Mauro Talevi commented on JBEHAVE-646:
--------------------------------------
The @Named annotation is intended for use with parameterised scenarios
(http://jbehave.org/reference/stable/parametrised-scenarios.html).
Hence, you cannot use it in conjunction with the normal parameter matching,
which uses natural ordering.
Have a look at the trader example module for uses of the @Named annotation.
> @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
