[ 
http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245810#action_245810
 ] 

Mauro Talevi commented on JBEHAVE-398:
--------------------------------------

The reason for having different parameter converters for different raw types is 
to distinguish the parameter List<String> from List<Number> (as you can see in 
the accept(Type) method.   
We can add a parameter converter for lists that delegates to the element 
parameter converter (which would be specified when instantiating the 
converter), so it can reused for different types of element converters, but I 
don't see the benefit of some of the elements in the patch.  In particular, 
changing the ParameterConverters from class to interface and changing the 
converter method signature would break backward compat.

> Provide generic parameter conversion to List<T>
> -----------------------------------------------
>
>                 Key: JBEHAVE-398
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-398
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 3.1.2
>            Reporter: Daniel Godfrey
>            Priority: Minor
>
> Currently to convert into a List<SomeType> it's necessary to register a 
> custom ParameterConverter. By default it already provides the ability to 
> convert into List<String> and List<subtype of Number>, but this should be 
> extended to support all instances of List<T> as it will reduce the duplicate 
> code necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
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


Reply via email to