Home » Search

About activation code

151-160 of 200Refresh
JDO Doc
1

clearGroups()

Method javax.jdo.FetchPlan FetchPlan clearGroups() Remove all active groups leaving no active fetch group. Returns: the FetchPlan Since: JDO 2.0
JDO Doc
1

getDataStoreConnection()

Method javax.jdo.PersistenceManager JDOConnection getDataStoreConnection() If this method is called while a datastore transaction is active, the object returned will be enlisted in the current transaction. If called in an optimistic transaction or outside an active transaction, the object returned
JDO Doc
1

getFetchGroups()

Method javax.jdo.PersistenceManagerFactory Set getFetchGroups() Get a modifiable Set containing a mutable copy of all currently active (in scope) fetch groups. The methods addFetchGroups ... of all currently active fetch groups Throws: SecurityException - if the caller is not authorized for JDOPermission ("getMetadata") Since: JDO 2.2
JDO Doc
1

isActive()

Method javax.jdo.Transaction boolean isActive() Returns whether there is a transaction currently active. Returns: true if the transaction is active. Since: JDO 1.0
JPA Doc
1

javax.persistence.EntityExistsException

and the entity already exists. The current transaction, if one is active, will be marked for rollback ... time. The current transaction, if one is active, will be marked for rollback. Since: JPA 1.0
JPA Doc
1

joinTransaction()

Method javax.persistence.EntityManager void joinTransaction() Indicate to the entity manager that a JTA transaction is active. This method should be called on a JTA application managed entity manager that was created outside the scope of the active transaction to associate it with the current JTA
JDO Doc
1

refreshAll()

Method javax.jdo.PersistenceManager void refreshAll() Refresh the state of all applicable instances from the data store. If called with an active transaction, all transactional instances will be refreshed. If called outside an active transaction, all nontransactional instances will be refreshed. Since: JDO 1.0 See Also: refresh(Object pc)
Issue
1

Enhanced classes problem

Hell, we have problem with the OEM enhancement licencing. When we used runtime licencing using machine activation code, everything works fine. But when we enhanced our classes with OEM licence ... the following system property. In your code before connecting to ObjectDB: System.setProperty
Issue
1

evalution limit error on digital ocean ubuntu

Trying to run the code on Digital Ocean Ubuntu instance. Generated license and set key in objectdb conf file. It gives below exceeds evaluation error when we try to run the code. Caused by: com ... .jpa.EMImpl.persist(EMImpl.java:434) Usually this is the result of setting the activation key in
Issue
1

Navigation through lazy loading from Detached Objects

. It will however make it much easier for many people who have coded against EclipseLink to migrate to ObjectDB. thanks ... for our system as coded. Build 2.3.6_16 includes an initial attempt to provide some sort of basic support ... ->e2:null] 1->e1:[] and when that line is active the output is: 1->e1:[2->e2:null] 1->e1:[2->e2