On Fri, Nov 27, 2015 at 5:39 PM, Senduran Balasubramaniyam <
[email protected]> wrote:
> Hi All,
>
> We have the following service reference
>
> @Reference(
> name = "mediation-engine",
> service = CarbonMessageProcessor.class,
> cardinality = ReferenceCardinality.AT_LEAST_ONE,
> policy = ReferencePolicy.DYNAMIC,
> unbind = "removeMediationEngine"
> )
> protected void addMediationEngine(CarbonMessageProcessor
> carbonMessageProcessor) {
> ContextHolder.getInstance().addEngine(carbonMessageProcessor);
> }
>
>
> but the bundle which has this service reference gets activated regardless
> of the referencing service (CarbonMessageProcessor service)
> Is this the expected behavior.
>
Bundle and DS components have different lifecycles. DS component activation
does not affect the activation of a bundle. I'm sure you are talking about
the activation of a DS component here.
There can be various reasons for this behaviour. First can you make sure
that all the packages required by this DS component are imported by the
bundle configuration? There can be a situation where a CNF error causing
this behaviour.
>
> Regards
> Senduran
>
> --
> *Senduran *
> Software Engineer,
> WSO2, Inc.; http://wso2.com/ <http://wso2.com/>
> Mobile: +94 77 952 6548
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware
Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>*
Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
