Re: Status of OBR

Hi David, Karaf Cave is still active and implements OSGi R6 Repository specification: it's the "replacement" of the "old" OBR specification. More than OBR, I would recommend to use Feature ResourcesRepository plug to Cave. I'm preparing a blog post about that. Regards JB On 11/14/2015

Re: Status of OBR

Hi JB, Super, thank you very much! I will be on the lookout for the blog post. Cheers, =David On Nov 14, 2015, at 6:36 PM, Jean-Baptiste Onofré wrote: > Hi David, > > Karaf Cave is still active and implements OSGi R6 Repository specification: > it's the "replacement" of

Re: 4.0.3 Karaf JPA problem.

I have an example in this direction: https://github.com/LuisLozano/karafExamples When using version 2.2.0 org.apache.aries.jpa.blueprint service is not displayed. However, using version 2.1.0 the service itself perfectly displayed. -- View this message in context:

Re: Custom Shell

Hi JB, Thanks for the hints! I’ll check these out. Best, =David On Nov 14, 2015, at 6:33 PM, Jean-Baptiste Onofré wrote: > Hi David, > > you can create commands and aliases, and use the RBAC/ACL to define the > commands available for users. > > You can also define a

Re: 4.0.3 Karaf JPA problem.

In Aries JPA 2.1.0 it was possible to colocate the persistence unit and the impl using the EntityManager. The reason is that in that version the EntityManager service is simply accessed using plain OSGi API. So the blueprint startup is not waiting for the service. The problem with this

Re: 4.0.3 Karaf JPA problem.

Hello. Thank you for the explanation. You mean if I want to use version 2.2.0 I have to do the following? 1. A blueprint bundle containing the persistence unit and DAO objects. 2. A blueprint bundle setting out the service that uses the DAO. The DAO objects are using the entityManager and