Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of julian.reschke@gmx.de
 designates 213.165.64.22 as permitted sender)
Message-ID: <4F4FD63D.3000103@gmx.de>
Date: Thu, 01 Mar 2012 21:04:13 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Jackrabbit Developers <dev@jackrabbit.apache.org>
Subject: JCR2SPI RepositoryConfig lifecycle
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

today I spent some time with a caching issue in my RepositoryService, 
only to find out that the lifecycle of the service is not necessarily 
the same as the one of the JCR2SPI RepositoryImpl.

See

     public Session login(Credentials credentials, String workspaceName) 
throws LoginException, NoSuchWorkspaceException, RepositoryException {
         SessionInfo info = 
config.getRepositoryService().obtain(credentials, workspaceName);
         try {
             if (info instanceof XASessionInfo) {
                 return new XASessionImpl((XASessionInfo) info, this, 
config);
             } else {
                 return new SessionImpl(info, this, config);
             }
         } catch (RepositoryException ex) {
             config.getRepositoryService().dispose(info);
             throw ex;
         }
     }

So a unless the RepositoryConfig caches the service, a new one will be 
built for each new JCR session.

Is this intentional? In which case we should augment the Javadoc.

Best regards, Julian