2010/12/16 Jukka Zitting <[email protected]>:
> Hmm, that's a side-effect of JCR-2555 [1], where we made the JCA packaging > independent of the underlying JCR implementation. There's no standard > repository shutdown mechanism in JCR, so the only way to do proper resource > management without custom JCR extensions is to make the repository > automatically startup and shutdown itself based on open sessions [2]. > > If this behavior is troublesome, please file an improvement request for > fixing this. We could solve the issue either by automatically keeping an open > session around until the JCA package gets undeployed or by adding special > handling for Jackrabbit repositories. > > [1] https://issues.apache.org/jira/browse/JCR-2555 > [2] https://issues.apache.org/jira/browse/JCR-245 > Created https://issues.apache.org/jira/browse/JCR-2847
