Yes, I could use a Service exposed by Blue Print. But a real difficult problem is "how could I manage the reference to the service".
While using "Spring DM" , it could maintenance the reference to service in a safely way: weak reference(which decouple direct reference from application to service, to avoid un-excepted issues when service is updated"), separate the life-cycle of service from client( etc: at run time, if service is not available, client could choose to wait a while until service available). But if I using a plain spring java object to invoke a blue print service, how could I achieve such a feature? > ----Original ----- > Sender: Johan Edstrom [mailto:[email protected]] >Date: 2011/6/13 13:00 > Receiver: [email protected] > Subject: Re: Blue Print VS Spring DM, which one should we choice? > > Expose services. > > On Jun 12, 2011, at 10:57 PM, ext2 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. > > > >
