Re: Status of OBR

[Jean-Baptiste Onofré]

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 04:41 AM, David Leangen wrote:


Hi!

I noticed that there is not much recent activity in Karaf-Cave. I also have a vague 
recollection of a recent email on the list saying that "OBR is deprecated".

Is anybody able to provide a little more clarity? I was planning on using the 
OBR feature for provisioning.


Thanks!
=David




--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Status of OBR

[David Leangen]

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 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 04:41 AM, David Leangen wrote:
>> 
>> Hi!
>> 
>> I noticed that there is not much recent activity in Karaf-Cave. I also have 
>> a vague recollection of a recent email on the list saying that "OBR is 
>> deprecated".
>> 
>> Is anybody able to provide a little more clarity? I was planning on using 
>> the OBR feature for provisioning.
>> 
>> 
>> Thanks!
>> =David
>> 
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: 4.0.3 Karaf JPA problem.

[conejo]

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: 
http://karaf.922171.n3.nabble.com/4-0-3-Karaf-JPA-problem-tp4043497p4043514.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Custom Shell

[David Leangen]

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 Karaf sub-shell.
> 
> Regards
> JB
> 
> On 11/14/2015 10:14 AM, David Leangen wrote:
>> 
>> Hi!
>> 
>> Is it possible to create a custom shell environment in addition to the 
>> existing shell in Karaf?
>> 
>> I would like to keep the existing shell available to qualified 
>> developers/operators, and provide a more restricted environment for less 
>> qualified operators, with only custom commands.
>> 
>> From what I see of gogo, it seems to be a singleton service.
>> 
>> 
>> Cheers,
>> =David
>> 
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: 4.0.3 Karaf JPA problem.

[Christian Schneider]

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 behaviour is that if for some reason the 
EntityManager service is not coming up then your blueprint will still 
start and block during the
first call until a timeout. This is probably not how you want your 
service to behave. You also had not indication in diag that something is 
wrong.


So in Aries JPA 2.2.0 I changed the code to correctly register a service 
reference for the EntityManager service in blueprint. So blueprint will 
delay the startup until
the service is coming up. You will also be able to see that the service 
is missing using diag.


So the behavior with the new version is like if you try to provide and 
use the same service in the same blueprint file. It will never start up. 
So you will have to separate the

persistence unit from the code using the EntityManager to make it work.

Of course it would be great to be able to colocate and have a good 
startup behaviour at the same time but I have not found a way to do so.
One option might be to register the service ref as optional but then you 
would have problems again if the EM does not come up.

If someone finds a good way then I am open to any suggestions about this.

Christian

Am 14.11.2015 um 14:14 schrieb conejo:

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: 
http://karaf.922171.n3.nabble.com/4-0-3-Karaf-JPA-problem-tp4043497p4043514.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: 4.0.3 Karaf JPA problem.

[conejo]

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 therefore have the
annotation @PersistenceContext

Another option (I guess) could leave everything as is but leaving
dataService.xml file defining the service as a separate bundle (or even
deployed in the deploy folder)



--
View this message in context: 
http://karaf.922171.n3.nabble.com/4-0-3-Karaf-JPA-problem-tp4043497p4043516.html
Sent from the Karaf - User mailing list archive at Nabble.com.