About activator

51-60 of 200Refresh
Manual
10

Running JPA Queries

if no transaction is active. On success - the executeUpdate method returns the number of objects
Manual
10

SELECT clause (JPQL / Criteria API)

are not associated with an EntityManager and changes to them when a transaction is active are not
Tutorial
10

Step 4: Add a Servlet Class

, the database connection (including the transaction if still active) is closed. The next step is adding a JSP page that will produce the guestbook page output.
Tutorial
10

Step 4: Add a Servlet Class

if still active) is closed. The next step is adding a JSP page that will produce the guestbook page output.
Issue
10

Explorer bug ? Objects seem to be missing from database in Class view, but are present as references

1st project)) INFO: RequestBean []: Created: com.greensoft.entity.Activity [null](TEST: the 1st activity) INFO: RequestBean []: Persisted: com.greensoft.entity.Activity [14](TEST: the 1st activity) INFO: RequestBean []: Created: com.greensoft.entity.Activity [null](TEST: the 2nd activity) INFO
JPA Doc
6

javax.persistence.EntityManager

). If this method is called when the entity manager is associated with an active transaction, the persistence ... IllegalArgumentException - if the instance is not a managed entity and a transaction is active Since: JPA 2.0 ... () Indicate to the entity manager that a JTA transaction is active. Indicate to the entity manager
JDO Doc
6

close()

from this PersistenceManagerFactory have no active transactions. If any PersistenceManager instances have an active transaction, throw a JDOUserException, with one nested JDOUserException for each PersistenceManager with an active Transaction. If there are no active transactions, then close
JDO Doc
5

checkConsistency()

with the datastore. This method has no effect if a transaction is not active. If a datastore transaction is active, this method verifies the consistency of instances in the cache against the datastore ... to do so. If an optimistic transaction is active, this method obtains a datastore connection and verifies
JDO Doc
5

flush()

Method javax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active ... transaction is active, this method obtains a datastore connection, synchronizes the cache
JDO Doc
5

getGroups()

Method javax.jdo.FetchPlan Set getGroups() Return an immutable Set containing the names of all active fetch groups. The Set is a copy of the currently active groups and will not change based on subsequent changes to the groups. Returns: an immutable Set containing the names of all currently active fetch groups Since: JDO 2.0