Hi Hiranya,

Just had a chat with Sameera. If the self-contained bundle has an explicit
rule not to import whichever embedded, it should not get wired to external
bundles. Shall we try that out and see?. Ideally we should have a single
Derby bundle but I am little reluctant to do changes to Qpid due to obvious
reasons ;-).

Thanks,
Danushka

On Mon, May 9, 2011 at 11:55 AM, Hiranya Jayathilaka <hira...@wso2.com>wrote:

>
>
> On Mon, May 9, 2011 at 11:49 AM, Danushka Menikkumbura 
> <danus...@wso2.com>wrote:
>
>> Even when the self-contained bundle does not import packages that are
>> embedded?
>>
>
> Seems that's the case. May be Sameera can explain this better?
>
> Thanks,
> Hiranya
>
>
>>
>> Danushka
>>
>>
>> On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka <hira...@wso2.com>wrote:
>>
>>>
>>>
>>> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura <
>>> danus...@wso2.com> wrote:
>>>
>>>> +1.
>>>>
>>>> I wonder why the Qpid bundle gets wired to the other Derby lib instead
>>>> of which is embedded?
>>>>
>>>
>>> I had a chat with Sameera about this. Apparently that's the normal OSGi
>>> behavior. Packages exported by other bundles get precedence over private
>>> packages.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>>>
>>>> Danushka
>>>>
>>>> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka 
>>>> <hira...@wso2.com>wrote:
>>>>
>>>>> I think the right solution is to introduce a separate Derby bundle
>>>>> (currently it's embedded in qpid). This bundle should contain everything
>>>>> needed for Qpid and ESB samples.
>>>>>
>>>>> Thanks,
>>>>> Hiranya
>>>>>
>>>>>
>>>>> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka <hira...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We are having some issues testing the DB mediator samples in ESB (with
>>>>>> Derby). When we deploy derby client libraries to the ESB, Qpid component
>>>>>> fails. Reason is when we deploy derby libraries to the ESB, the qpid
>>>>>> component gets wired to that instead of the embedded derby binaries. Any
>>>>>> idea how to fix this?
>>>>>>
>>>>>> Thanks
>>>>>> --
>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Carbon-dev mailing list
>>>> Carbon-dev@wso2.org
>>>> http://mail.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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to