[ 
https://issues.apache.org/jira/browse/ARIES-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571169#comment-15571169
 ] 

Grzegorz Grzybek commented on ARIES-1407:
-----------------------------------------

ARIES-805 seems to be against Blueprint spec. and:
{code:xml}
    <service id="connectionFactoryService" ref="pooledConnectionFactory" 
interface="javax.jms.ConnectionFactory">
        <registration-listener registration-method="register">
                <bean class="com.mycompany.blueprint.ExitGracePeriodNotifier">
                        <property name="blueprintContainer" 
ref="blueprintContainer"/>
                </bean>
        </registration-listener>
    </service>
{code}

doesn't look like a good way to detect when slave broker becomes master.
You're mixing two lifecycles here - this from Blueprint (spec) and from 
ActiveMQ master-slave configuration.

What is the *real* goal you want to achieve? To be notified that ActiveMQ 
broker becomes master? Do you really want to restart Blueprint container in 
this case?

You can "think out of blueprint" here and try using some JMX listener or 
ActiveMQ discovery.

This issue is actually _no fix_.

> 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)

Reply via email to