I feel that we can provide a proper OSGi solution without taking a dependency on OSGi APIs by using declarative service POJOs.
Azeez On Sat, May 16, 2009 at 2:02 AM, Ruwan Linton <[email protected]> wrote: > Afkham Azeez wrote: >> Hi Folks, >> The synapse-extensions bundle was a fragment of the synapse-core >> bundle. This was causing many issues. The fragment's imported packages >> were conflicting with the host's imported packages, hence the fragment >> was always in the INSTALLED state. I made this fragment into a fully >> fledged bundle, and was able to resolve all of these issues. I have >> committed this change to the synapse carbon-platform 1.6 branch. (we >> can revert it if necessary). Will this break anything? What was the >> reason for making synapse-extensions a fragment in the first place? >> > The reason was to get the extension mediators work with the service > providers model. Basically we use the sun's service provider model to > load any extension mediators and the loading task will be done by the > synapse core and these service provider resources of the extensions > bundle cannot be seen to the core bundle if it is not a fragment of the > core. > > I think for this milestone we can go with this change.... and find a > solution to the original problem for the next milestone. > > Thanks, > Ruwan > > -- > Ruwan Linton > Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 Inc.; http://wso2.org > email: [email protected]; cell: +94 77 341 3097 > blog: http://ruwansblog.blogspot.com > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- -- Afkham Azeez [email protected] WSO2 Inc. http://wso2.com Blog: http://afkham.org _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
