Re: Blueprint or DS or what to use?

Andreas you are crossing or about to cross a bridge we are crossing at the moment. We also have a SpringDM based application. It is 3+ years in production and so a change as large as moving away from SpringDM is very disruptive. For the most part we considered only Aries Blueprint vs DS. However as

Re: Declarative service / serviceTracker

Hi Morgan, yes, I know (as it was we discussed): I just explained for the others ;) I gonna take a look on your code. Regards JB On 03/20/2016 11:17 AM, Morgan wrote: Hey guys, To be clear , the @JPA annotation does generate the persistence.xml during compile time. That was the purpose of th

static content apparently not working in Karaf 4.0.4 via jetty config

/doc ../../doc true jvm 1| 2016-03-16 08:08:39,183 | WARN | tp1085327538-940 | Response | 217 - org.eclipse.jet

Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default

Hi, I agree with Lukasz: I have no problem to document and improve the way to include such appender in custom distribution, but I don't think it's a good idea to have it shipped by default. I could also be a Decanter new collector/appender (as we already have a log collector/appender). Reg

Re: Declarative service / serviceTracker

Hey guys, To be clear , the @JPA annotation does generate the persistence.xml during compile time. That was the purpose of the new @JPA annotation. The question was indeed on the service reference. The purpose is to execute the bundle when a datasource x is recognized by the service registry.

Re: Spring 4 Bundle spring-data-neo4j Contains Wrong Import-Package version restrictions for neo4j

Is there a better mailing list for questions about the thirdparty OSGi bundles created for Karaf/ServiceMix? Thanks, Jake -- View this message in context: http://karaf.922171.n3.nabble.com/Spring-4-Bundle-spring-data-neo4j-Contains-Wrong-Import-Package-version-restrictions-for-neo4j-tp4045782p

Re: static content apparently not working in Karaf 4.0.4 via jetty config

On Fri, Mar 18, 2016 at 6:46 AM, Achim Nierbeck wrote: > > http://ops4j.github.io/pax/web/4.2.x/index.html#_advanced_jetty_configuration For my particular application, zero java code is actually preferable. Anyhow, why would configuring it that way prevent Jetty from try to write to closed conn

Re: Declarative service / serviceTracker

Hi guys, I think the purpose of @jpa annotation is not "only" the datasource. The @jpa annotation should also define additional attribute like the provider. Thanks to that, karaf-boot will be able to generate the persistence.xml and additional resources more than the datasource. IMHO, regar

Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default

Hi Valdimir, by feature, I meant "a simple way" to provide/add it (not necessary a Karaf feature) ;) Probably the easier way now is to document how to do it in the dev guide with an associated sample. Regards JB On 03/19/2016 03:03 PM, Владимир Коньков wrote: Hi Jean-Baptiste! We activel

RE: Blueprint or DS or what to use?

We use Blueprint mainly to have a code which makes use of services but without dealing with OSGi or annotations (as far as possible => few wappers). As long with the maven-bundle-plugin it is a kind of magic. I would say Blueprint+Maven+Karaf makes things really easy. I would suggest to make a

Re: Karaf assembly

On Wednesday 16 March 2016 05:18:39 conejo wrote: > Hello hi, > When I use the maven archetype, distribution generated does not include the > jar files that you can find in lib in a downloaded karaf (especially > lib/endorsed jar files). > > Is there any way to include libraries of karaf.home/l