|
Spring Framework example source code file (JdoAccessor.java)
The Spring Framework JdoAccessor.java source code/* * Copyright 2002-2006 the original author or authors. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ package org.springframework.orm.jdo; import javax.jdo.JDOException; import javax.jdo.PersistenceManager; import javax.jdo.PersistenceManagerFactory; import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; import org.springframework.beans.factory.InitializingBean; import org.springframework.dao.DataAccessException; /** * Base class for JdoTemplate and JdoInterceptor, defining common * properties such as PersistenceManagerFactory and flushing behavior. * * <p>Note: With JDO, modifications to persistent objects are just possible * within a transaction (in contrast to Hibernate). Therefore, eager flushing * will just get applied when in a transaction. Furthermore, there is no * explicit notion of flushing never, as this would not imply a performance * gain due to JDO's field interception mechanism (which doesn't involve * the overhead of snapshot comparisons). * * <p>Eager flushing is just available for specific JDO providers. * You need to a corresponding JdoDialect to make eager flushing work. * * <p>Not intended to be used directly. See JdoTemplate and JdoInterceptor. * * @author Juergen Hoeller * @since 02.11.2003 * @see JdoTemplate * @see JdoInterceptor * @see #setFlushEager */ public abstract class JdoAccessor implements InitializingBean { /** Logger available to subclasses */ protected final Log logger = LogFactory.getLog(getClass()); private PersistenceManagerFactory persistenceManagerFactory; private JdoDialect jdoDialect; private boolean flushEager = false; /** * Set the JDO PersistenceManagerFactory that should be used to create * PersistenceManagers. */ public void setPersistenceManagerFactory(PersistenceManagerFactory pmf) { this.persistenceManagerFactory = pmf; } /** * Return the JDO PersistenceManagerFactory that should be used to create * PersistenceManagers. */ public PersistenceManagerFactory getPersistenceManagerFactory() { return persistenceManagerFactory; } /** * Set the JDO dialect to use for this accessor. * <p>The dialect object can be used to retrieve the underlying JDBC * connection and to eagerly flush changes to the database. * <p>Default is a DefaultJdoDialect based on the PersistenceManagerFactory's * underlying DataSource, if any. */ public void setJdoDialect(JdoDialect jdoDialect) { this.jdoDialect = jdoDialect; } /** * Return the JDO dialect to use for this accessor. * <p>Creates a default one for the specified PersistenceManagerFactory if none set. */ public JdoDialect getJdoDialect() { if (this.jdoDialect == null) { this.jdoDialect = new DefaultJdoDialect(); } return this.jdoDialect; } /** * Set if this accessor should flush changes to the database eagerly. * <p>Eager flushing leads to immediate synchronization with the database, * even if in a transaction. This causes inconsistencies to show up and throw * a respective exception immediately, and JDBC access code that participates * in the same transaction will see the changes as the database is already * aware of them then. But the drawbacks are: * <ul> * <li>additional communication roundtrips with the database, instead of a * single batch at transaction commit; * <li>the fact that an actual database rollback is needed if the JDO * transaction rolls back (due to already submitted SQL statements). * </ul> */ public void setFlushEager(boolean flushEager) { this.flushEager = flushEager; } /** * Return if this accessor should flush changes to the database eagerly. */ public boolean isFlushEager() { return flushEager; } /** * Eagerly initialize the JDO dialect, creating a default one * for the specified PersistenceManagerFactory if none set. */ public void afterPropertiesSet() { if (getPersistenceManagerFactory() == null) { throw new IllegalArgumentException("persistenceManagerFactory is required"); } // Build default JdoDialect if none explicitly specified. if (this.jdoDialect == null) { this.jdoDialect = new DefaultJdoDialect(getPersistenceManagerFactory().getConnectionFactory()); } } /** * Flush the given JDO persistence manager if necessary. * @param pm the current JDO PersistenceManager * @param existingTransaction if executing within an existing transaction * (within an existing JDO PersistenceManager that won't be closed immediately) * @throws JDOException in case of JDO flushing errors */ protected void flushIfNecessary(PersistenceManager pm, boolean existingTransaction) throws JDOException { if (isFlushEager()) { logger.debug("Eagerly flushing JDO persistence manager"); getJdoDialect().flush(pm); } } /** * Convert the given JDOException to an appropriate exception from the * <code>org.springframework.dao hierarchy. * <p>Default implementation delegates to the JdoDialect. * May be overridden in subclasses. * @param ex JDOException that occured * @return the corresponding DataAccessException instance * @see JdoDialect#translateException */ public DataAccessException convertJdoAccessException(JDOException ex) { return getJdoDialect().translateException(ex); } } Other Spring Framework examples (source code examples)Here is a short list of links related to this Spring Framework JdoAccessor.java source code file: |
... this post is sponsored by my books ... | |
#1 New Release! |
FP Best Seller |
Copyright 1998-2024 Alvin Alexander, alvinalexander.com
All Rights Reserved.
A percentage of advertising revenue from
pages under the /java/jwarehouse
URI on this website is
paid back to open source projects.