> -----original----- > Sender: Gert Vanthienen [mailto:[email protected]] > Date: 2011/6/13/ 13:33 > Receiver: [email protected] > Subject: Re: Blue Print VS Spring DM, which one should we choice? > > L.S., > > > As Johan already said, you can build parts of your application using > Blueprint and others bits using Spring (DM) and then use the OSGi > Service Registry to expose services and tie things together. That > way, you can still use whatever features you have available in either > framework. BTW, you can also just instantiate the helper classes that > come with the Spring Framework from within a Blueprint XML file > (though you probably have to configure > init-method="afterPropertiesSet")
Thanks Gert Vanthienen. Do you means I can use a spring bean in Blue-Print xml? > Regards, > > Gert Vanthienen > ------------------------ > FuseSource > Web: http://fusesource.com > Blog: http://gertvanthienen.blogspot.com/ > > > > On Mon, Jun 13, 2011 at 6:57 AM, ext2 <[email protected]> wrote: > > Hi: > > Blue Print and Spring DM both support declarative OSGI Service's > > publish and reference usage. > > While using Spring DM , the Thread Context Class Loader feature > > sometimes is convenience, but sometime cause unexpected issue. (Recently I > > have meat a Bundle uninstalled exception caused by spring dm's thread > > context class loader, which I have said in another mail). > > While using Blue Print, it doesn't force to use thread Context Class > > Loader. So it's better than spring dm at this point. > > Spring DM is very easy to integrate in spring application. But while > > using Blue Print, I have no ideas how could I integrate it with Spring, does > > anyone know how to do this? > > > > Thanks any suggestion. > > > > > >
