Hi, On Thu, Oct 22, 2009 at 1:35 PM, Felix Meschberger <[email protected]> wrote: > Hmm, the fine print is "usually" ... Why not define an API to let go off > the repository, which will be doing nothing in GC-supported cases and > cleanup in other cases ?
Where would you "usually" need such an API? A typical client needs to be able to connect to an existing repository without worrying about the repository lifecycle. The lifecycle becomes important only when the client uses the repository in embedded mode, in which case it already has a direct dependency to jackrabbit-core and can (and IMHO should) directly use the RepositoryImpl class. BR, Jukka Zitting
