[jira] Resolved: (ARIES-389) Problem with type converters which produce a null result.

["Valentin Mahrwald (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARIES-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Valentin Mahrwald resolved ARIES-389.
-------------------------------------

    Resolution: Fixed

Thanks for the patch Wolfgang! I have committed it in revision 990789.

> Problem with type converters which produce a null result.
> ---------------------------------------------------------
>
>                 Key: ARIES-389
>                 URL: https://issues.apache.org/jira/browse/ARIES-389
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.1, 0.2, Incubation
>         Environment: apache-karaf-2.0.0, running under jre-1.6 under Windows or Linux.
>            Reporter: Wolfgang Glas
>            Assignee: Valentin Mahrwald
>         Attachments: aries-blueprint-null-conversion-svn988025-r1.patch, aries-blueprint-null-conversion-svn988025.patch
>
>
> In order to inject ConfigAdmin properties into blueprint beans we wrote a ConfigPropertyAccessor class, which produces ConfigProperty beans, which then may be injected into other bean's properties on behalf of a special type converter.
> The type converter in necessary in order to correctly deal with unconfigured aka null values.
> You may have a look at our open source library under
>   http://maven.clazzes.org/org/clazzes/util/0.9.1/
> where the classes are contained in the package org.clazzes.util.osgi.
> When applying all this stuff on null config values in any aries blueprint version available to me at the time of writing, the null return value of the type converter has the effect, that the conversion algorithm in AggregateConverter.java continues with it's conversion machinery for all known types causing it to fail with an Exception.
> However in "OSGi Service Platform Release 4, Service Compendium 4.2" in section 121.9.3 on pages 689-690, there is no hint ,taht the conversion algorithm should continue after step 2, when a type converter has been selected in step 1.
> I will attach a fix, which fixes my problem for svn rev. 988025 on aries trunk.
> Please review my patch and let me know, whether I shoukld improve it or you are able to apply it to the aries trunk.
>   Best regards, Wolfgang Glas

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.