jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Br┬čuen <dbr...@saltation.de>
Subject Re: Repository Lock Problem in JEE-Environment
Date Thu, 23 Aug 2007 15:22:30 GMT
Hi!

Marcel May wrote:
> Can you use |@PreDestroy annotated method ?

Yes, that's worth a try, at least for stateful session beans 
(@PrePassivate, @PostPassivate).	

How do other folks use Jackrabbit in a JEE Environment, especially in a 
session bean? Do you acquire the repository in every single method call 
via JNDI, or do you store the repository handle in a member variable of 
the bean?

If I get it correctly there can be only one single bean accessing the 
repository, since the repository can talk to only one single 
application. As a consequence there would be a locking-problem if the 
container decides to create another bean to handle requests, which is odd.

cheers,
Dan


Mime
View raw message