On Mon, Mar 5, 2012 at 7:03 PM, Pradeep Fernando <[email protected]> wrote:
> Hi all, > > The JPA uses provider architecture. There it loads providers using java > spi mechanism. The problem is with unique classLoaders, this does not work > in OSGi. (earlier we used to load them all using > application/carbon-bootstrap classLoader by placing them in outer lib) > > two viable options. > > 1. go for OSGi JPA implementation. (eclipse gemini, apache aries are two > impls) > This looks like the right thing to do. The development overhead will be high but will be beneficial in the long run. Since our platform is based on OSGi, problems such as this one are best solved in an OSGi specific manner. Any other solution would be more or less a hack and will break when we make significant changes to the underlying framework. Thanks, Hiranya > 2. use fragmenting mechanism to laod bundles using the same classLoader. > > > Any other suggestions ? > > --Pradeep > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
