[
https://issues.apache.org/jira/browse/ARIES-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562261#comment-15562261
]
metatech commented on ARIES-1407:
---------------------------------
What I meant was : we started using ServiceMix 4.3.0 in 2011 (Blueprint
0.2-incubating), then migrated to 4.4.2 (Blueprint 0.3.1) in 2012, and to 4.5.3
(Blueprint 0.3.2) in 2014, and to 5.4.1 (Blueprint 1.4.3) in 2015. The
behaviour changed only in the last Blueprint version. But please rest assured
that we did not stay on 0.2 for all those years...
BTW, we do those kind of small enhancements to avoid inaccuracies in the status
or monitoring of ServiceMix, because this simplifies the support of our
mission-critical environment.
> Service (un)registration listener not called anymore
> ----------------------------------------------------
>
> Key: ARIES-1407
> URL: https://issues.apache.org/jira/browse/ARIES-1407
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Environment: Servicemix 5.4.1
> Reporter: metatech
> Attachments: blueprint_registration_listener_fix_v2.patch
>
>
> Service (un)registration listeners are not called anymore since Blueprint
> 1.4.0.
> There are 2 booleans in the "ServiceRecipe" class which are tested against
> the wrong values.
> Please find a patch which makes them work again with Blueprint 1.4.3.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
