Achim, I have finally succeed :). My solution to introduce a flag in gemini works well. More formally aries blueprint handle standard blueprint bundle and Gemini-Blueprint handle only Spring ready bundles. And clearly the current version of Gemini-Blueprint (1.0) is not compatible with String 3.1.
Romain Le mardi 5 juin 2012, Romain Gilles a écrit : > I think I can also add an option to genimi-blueprint to disable blueprint > support and activate only gemini spring only. The extender already work > like this if it is a Pre-4.2 OSGi platform. > > What do you think? > > Romain. > > PS: cloud you give the doc entry (url) for region management? > > > > 2012/6/5 Achim Nierbeck <[email protected]> > > Romain, > > no problem someone will be there helping :) > > regards, Achim > > 2012/6/5 Romain Gilles <[email protected]>: > > Hi Achim, > > I just now found a github clone of the original gemini-blueprint and the > > guys have already patch it to support spring 3.1. They have do almost the > > same things as I have done so I will use their vesion. > > Project: https://github.com/glyn/Gemini-Blueprint > > Repository: https://github.com/glyn/Gemini-Blueprint.git > > > > I will try to use this version with karaf 3.0 (trunk) and the regions. > > I will need help for sure. > > > > Romain > > > > 2012/6/5 Achim Nierbeck <[email protected]> > >> > >> Hi Romain, > >> > >> I think a never version of Gemini is needed to work with spring 3.1 > >> it was something like 1.0.1-SNAPSHOT > >> > >> regards, Achim > >> > >> 2012/6/5 Romain Gilles <[email protected]>: > >> > Hi Achim, > >> > It sounds good :). On my side I have tried to install gemini 1.0 + > >> > spring > >> > 3.1.1 on a karaf 2.2.7 and it is not fun at all. > >> > I'm surprise but I think gemini-blueprint does not compile with the > last > >> > version of spring even if the version range support it [3.0,4.0) > >> > > >> > It seams that spring 3.1 introduce a API compatibility break from the > >> > version 3.0. > >> > > >> > Romain. > >> > > >> > 2012/6/5 Achim Nierbeck <[email protected]> > >> >> > >> >> Hi Romain, > >> >> > >> >> Since Apache Karaf uses Apache Aries for the underlying blueprint > >> >> implementation there is no easy way around this with the current > >> >> version of Karaf. > >> >> Though with Karaf 3.0 it is possible to "mix" both implementations > due > >> >> to the used regions. You could try with the latest SNAPSHOT of Karaf > >> >> 3.0 to find out. > >> >> Gemini will be supported only inside it's own "Region" :) > >> >> > >> >> To make sure you are actually using Gemini instead of Aries I think > >> >> you need to add a certain flag (which I don't recall right now) > >> >> So I'll try to dig around this and will let you know. Or someone who > >> >> knows will jump up and point out :) > >> >> > >> >> regards, Achim > >> >> > >> >> 2012/6/5 Romain Gilles <[email protected]>: > >> >> > Do you mean that gemini-blueprint is the only way to mix osgi with > >> >> > spring; > >> >> > and you are not confident that it is working with karaf? > >> >> > > >> >> > Romain. > >> >> > > >> >> > 2012/6/5 Christian Schneider <[email protected]> > >> >> >> > >> >> >> Aries blueprint does not support the normal spring namespaces. It > >> >> >> only > >> >> >> supports the blueprint namespace. I have never seen gemini run in > >> >> >> karaf > >> >> >> so I > >> >> >> am not sure if this is possible. > >> >> >> > >> >> >> If you only use spring for the non OSGi tests you might try > >> >> >> blueprint > >> >> >> and > >> >> >> pax exam or the karaf testing framework instead. This way it will > >> >> >> all > >> >> >> be > >> > > >
