On 09/30/2011 08:13 PM, Neil Bartlett wrote: > Hi Ferry, > > Could you clarify question 1? I don't understand what you're asking for > there.
ofcourse :-) I converted the JNotify library to an OSGi service bundle that use DS. Now to make it even better I'd like to also use blueprint: blueprint for the internal wiring and DS for the service publication. However, this library has platform specific parts, you saw a snippet of the native libraries contained within the bundle. The library has a single interface for all platforms and that facade is 'just' a wrapper around different implementations for different platforms. I'd like to define wired beans for these platforms and wire the correct - platform specific bean - into the facade. hope that is clearer. > > In reply to point 2, and not disagreeing with anything Mike said… > standard OBR (both the current released version and the new RFC) can do > this too, but you need an index generator that knows about DS. > > The generator would need to recognise a bundle that contains > Service-Component declarations and add requirements for both the DS > runtime and possibly the referenced references, and capabilities for the > offered services. It would also need to recognise a DS runtime bundle to > declare the DS capability. > > Currently the de-facto standard OBR generator is bindex, and it does NOT > do any of these things. Apache Aries has its own generator that does > something very like the above, except for Blueprint rather than DS. > Nimble's generator is very powerful and extensible but it uses a > proprietary repository format (though it will use the new OBR standard > format by the time it is released). > > Regards, > Neil > > > On Friday, 30 September 2011 at 17:39, Ferry Huberts wrote: > >> On 09/30/2011 04:21 PM, Mike Francis wrote: >>> Ferry >>> >>> In response to question 2 - Nimble will do this for you without you >>> having >>> to make any changes to the Manifest or JAR. In Nimble we inspect a >>> bundle to >>> see if it uses declarative services (or other extender bundles) and >>> resolve >>> those service dependencies alongside your bundles. You can also set >>> policies >>> to manage the deployment e.g. selecting equinox/felix DS providers or >>> Tomcat/Jetty for a WAR. >>> >>> Nimble is available for download from www.paremus.com/downloads >>> <http://www.paremus.com/downloads>. You can >>> take just Nimble Core or the Nimble Distribution which includes our >>> Remote >>> Service Admin implementation. >>> >>> Regards >>> Mike >> >> Thanks Mike! >> >> will take a look :-) >> >>> -----Original Message----- >>> From: osgi-dev-boun...@mail.osgi.org >>> <mailto:osgi-dev-boun...@mail.osgi.org> >>> [mailto:osgi-dev-boun...@mail.osgi.org] >>> On Behalf Of Ferry Huberts >>> Sent: 29 September 2011 22:29 >>> To: osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >>> Subject: [osgi-dev] 2 questions >>> >>> Hi list, >>> >>> I have 2 questions: >>> >>> 1- Can I do platform dependent blueprint wiring? >>> Just like I can do: >>> >>> Bundle-NativeCode: lib/linux/i686/lib.so;osname=Linux;processor=x86,\ >>> lib/linux/x86_64/lib.so;osname=Linux;processor=x86-64 >>> >>> 2- Is there a way to express in the manifest or jar what services are >>> needed >>> from the platform? For example: if I could specify that DS is needed >>> for a >>> DS component then my run configurations/deployments could be >>> automatically >>> verified (and even generated, think bndtools) >>> >>> -- >>> Ferry Huberts >>> _______________________________________________ >>> OSGi Developer Mail List >>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >>> >>> _______________________________________________ >>> OSGi Developer Mail List >>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> >> -- >> Ferry Huberts >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >> https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev -- Ferry Huberts _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
