Examples of JcrInterceptor

• org.springmodules.jcr.JcrInterceptor
  This interceptor binds a new Jcr Session to the thread before a method call, closing and removing it afterwards in case of any method outcome. If there already is a pre-bound Jcr Session (e.g. from JcrTransactionManager, or from a surrounding JCR-intercepted method), the interceptor simply participates in it.

  Application code must retrieve a JCR Session via the JcrSessionFactoryUtils.getSession method, to be able to detect a thread-bound Jcr Session. It is preferable to use getSession with allowCreate=false, if the code relies on the interceptor to provide proper session handling. Typically, the code will look as follows:

   public void doJcrAction() { Session session = JcrSessionFactoryUtils.getSession(this.jsf, false); try { ... } catch (RepositoryException ex) { throw JcrSessionFactoryUtils.convertJcrAccessException(ex); } } 

  Note that the application must care about handling RepositoryExceptions itself, preferably via delegating to the JcrSessionFactoryUtils.convertJcrAccessException method that converts them to exceptions that are compatible with the org.springframework.dao exception hierarchy (like JcrTemplate does).

  This class can be considered a declarative alternative to JcrTemplate's callback approach. The advantages are:

  • no anonymous classes necessary for callback implementations;
  • the possibility to throw any application exceptions from within data access code.

  The drawbacks are:

  • the dependency on interceptor configuration;
  • the delegating try/catch blocks.

  @author Costin Leau

Examples of org.springmodules.jcr.JcrInterceptor