On Wed, Jan 19, 2011 at 1:46 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote:

>
>
> On Tue, Jan 18, 2011 at 5:26 PM, Shammi Jayasinghe <sha...@wso2.com>wrote:
>
>> Hi ,
>>
>> In the process of providing multi tenant support for CEP , there are two
>> components (broker-manager and cep) that are needed to implement the
>> interface Axis2ConfigurationContextObserver.
>> In that case,  i need to control the order of  invoking of these
>> implementations since CEP is depend on broker-manager and , broker manager
>> has to load some resources from registry which are needed for CEP.
>>
>>
>> What is the possible way to do this ?
>>
>
> I think observers get notified in the order they were registered.
>

I think the problem here is not invoking the observers in the same order
bundles have register them.

In fact carbon components get invoked in an order controlled by the
declarative services. If the the tenent observers also get invoked in the
same order (i.e registered order) that would be sufficient for most cases.

thanks,
Amila.


> So if you can control the registration order, then you have a guarantee
> regarding the order of notification. If not we will have to add a method to
> the observer registration API which will enable the programmer to enforce
> this kind of restrictions. For an example:
>
> addAfter(Observer o1, Observer o2)
> addBefore(Observer o1, Observer o2)
>
> Thanks,
> Hiranya
>
>
>>
>> Thanks
>> --
>> Best Regards,*
>>
>> Shammi Jayasinghe*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
>> mobile: +94 71 4493085
>>
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> _______________________________________________
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to