[jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-125) Ambiguity on setters

[Ales Justin (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-125?page=all ]

Ales Justin resolved JBMICROCONT-125.
-------------------------------------

    Fix Version/s: JBossMC_2_0_0_CR1
       Resolution: Done

Removed single setter property check from AbstractBeanInfoFactory.
Added property type check when resolving PropertyInfo.
First we test (String) equality of types, then class type assigment and progression (todo).

Also added getType method to PropertyMetaData - more info to determine the right property to use.

> Ambiguity on setters
> --------------------
>
>                 Key: JBMICROCONT-125
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-125
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: BeanInfo
>    Affects Versions: JBossMC_2_0_0 Beta
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>             Fix For: JBossMC_2_0_0_CR1
>
>
> There is an ambiguity when it comes to javabeans with only setters,
> e.g.
> setSomething(Integer);
> setSomething(String);
> Currently, the implementation cannot use the getter to decide which is the correct setter.
> Instead it says that 'something" is not a property if there are multiple setters.
> Maybe this can be relaxed and we let the Configurator pick which one based upon
> what users decides to use?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira