aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Mahrwald (JIRA)" <>
Subject [jira] Commented: (ARIES-389) Problem with type converters which produce a null result.
Date Tue, 31 Aug 2010 07:24:53 GMT


Valentin Mahrwald commented on ARIES-389:

Hi Wolfgang,

the 0.2 release is already in progress and on the fifth release candidate. At this stage I
think - after talking this over with Zoe who does the release - we only really want to respin
for show stopper defect. 

That being said if you really need this, please feel free to comment (or vote -1) on the release
discussion / vote thread and we will have the discussion there with everyone involved. Also,
if there is another respin for any other reason, we'll try to get this in.



> Problem with type converters which produce a null result.
> ---------------------------------------------------------
>                 Key: ARIES-389
>                 URL:
>             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
> You may have a look at our open source library under
> 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 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.

View raw message