Internal Website Search

Mahmoud Defining default listeners is one of the few things that currently require XML metadata ... Is there a way using em.getDelegate() and then using objectdb api ? I would like to do specifics actions ... chapter 3 of the manual. You may also register listener using the JDO API , which is not documented but supported by ObjectDB. support Support

In a class how do I define which are the fields to be stored? (using JDO API ) It's using persistence-modifier="persistent" ? If I have a class with 40 fields and I only want to store ... @NonPersistent  (starting JDO 2.1 you can use annotations instead of XML metadata ). support Support

metadata files:                       ... try I changed only the metadata to this:               ... :82)   I thought that simply changing JDO metadata is not sufficient. Should it be sufficient

(JpaQuery.java:719) - locked (a com.objectdb.jdo.PMImpl) at com.agile.hummingbird. API .handleQuery( API .java:3020) at com.agile.hummingbird. API .directRequest( API .java:852) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:614) at com.agile.hummingbird.WebSocketServerListener.onWebSocketText

.   It looks like JDO is the preferred API for me (because ObjectDB FAQs lead me to believe ... solution.  =)   Thanks! CBE CBE Hmm, I just found this link:  https://www.objectdb.com/ api ... API reference unique to ObjectDB, or is it an exact copy of some JDO 2.x API that I could find

I prefer to use the package.jdo XML metadata rather than annotations, but you don't ... that it corresponds to the XML element which is one way to specify indexes in XML metadata ... whether objectdb supports this? spiffy Jonathan Harley JDO XML metadata , although not documented in ObjectDB 2

JPA Interface CriteriaDelete Type Parameters: - the entity type that is the target of the delete Super Interfaces: CommonAbstractCriteria The CriteriaDelete interface defines functionality for performing bulk delete operations using the Criteria API Criteria API bulk delete operations map directly

is found not to be a Java Persistence query language SELECT query or a Criteria API query Since: JPA 2.0 ... an object of the specified type to allow access to the provider-specific API . If the provider's query

SELECT query or a Criteria API query Inherited from: Query Since: JPA 2.0 int getMaxResults ... -specific API . If the provider's query implementation does not support the specified class

JPA Interface CriteriaBuilder Used to construct criteria queries, compound selections, expressions, predicates, orderings. Note that Predicate is used instead of Expression in this API in order ... Criteria API Queries article explains how to use CriteriaBuilder . Public Methods Expression abs

The Paths and Types in JPQL and Criteria API article explains how to use Path . Public Methods ... attribute. Note: Applications using the string-based API may need to specify the type resulting from

JPA Interface CriteriaUpdate Type Parameters: - the entity type that is the target of the update Super Interfaces: CommonAbstractCriteria The CriteriaUpdate interface defines functionality for performing bulk update operations using the Criteria API . Criteria API bulk update operations map

.hummingbird.CT_Container.computeContainer(CT_Container.java:214) com.agile.hummingbird. API .handleGetContainer( API .java:3130) com.agile.hummingbird. API .directRequest( API .java:965) com.agile.hummingbird. API .handleWebSocketRequest( API .java:808) com.agile.hummingbird.WebSocketServerListener

JPA Interface Selection Type Parameters: - the type of the selection item Super Interfaces: TupleElement The Selection interface defines an item that is to be returned in a query result. Since: JPA 2.0 The SELECT clause (JPQL / Criteria API ) article explains how to use Selection . Public Methods

JPA Interface Root Type Parameters: - the entity type referenced by the root A root type in the from clause. Query roots always reference entities. Since: JPA 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Root . Public Methods EntityType getModel () Return the metamodel

part of an API call, at, flush or at commit time. The current transaction, if one is active, will be not

JPA Method in javax.persistence.EntityManagerFactory T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's EntityManagerFactory implementation does not support the specified class, the PersistenceException

when an pessimistic locking conflict occurs. This exception may be thrown as part of an API call, a flush or at commit

and Criteria API article explains how to use Predicate . Public Methods List getExpressions () Return

JPA Method in javax.persistence.criteria.Path Path get (   String attributeName ) Create a path corresponding to the referenced attribute. Note: Applications using the string-based API may need to specify the type resulting from the get operation in order to avoid the use of Path

locking conflict occurs. This exception may be thrown as part of an API call, a flush or at commit

well; however, support for the Java SE bootstrapping APIs is not required in container environments

JPA Method in javax.persistence.Query T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's query implementation does not support the specified class, the PersistenceException is thrown. Parameters: cls

JPA Method in javax.persistence.Query LockModeType getLockMode () Get the current lock mode for the query. Returns null if a lock mode has not been set on the query object. Return: lock mode Throws: IllegalStateException - if the query is found not to be a Java Persistence query language SELECT query or a Criteria API query Since: JPA 2.0

: Applications using the string-based API may need to specify the type resulting from the get operation in

JPA Interface Order An object that defines an ordering over the query results. Since: JPA 2.0 The ORDER BY clause (JPQL / Criteria API ) article explains how to use Order . Public Methods Expression getExpression () Return the expression that is used for ordering. Return: expression used

JPA Annotation Attribute in javax.persistence.SqlResultSetMapping String name default null The name given to the result set mapping, and used to refer to it in the methods of the Query and StoredProcedureQuery APIs . Since: JPA 1.0

to the result set mapping, and used to refer to it in the methods of the Query and StoredProcedureQuery APIs . Since: JPA 1.0

JPA Method in javax.persistence.Cache T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's Cache implementation does not support the specified class, the PersistenceException is thrown. Parameters: cls

to allow access to the provider-specific API . If the provider's Cache implementation does not support

JPA Method in javax.persistence.EntityManager T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's EntityManager implementation does not support the specified class, the PersistenceException is thrown

JPA Interface Join Type Parameters: - the source type of the join - the target type of the join A join to an entity, embeddable, or basic type. Since: JPA 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Join . Public Methods Attribute getAttribute () Return the metamodel

JPA Method in javax.persistence.criteria.CriteriaQuery CriteriaQuery select (   Selection  selection ) Specify the item that is to be returned in the query result. Replaces the previously specified selection(s), if any. Note: Applications using the string-based API may need

.endAction(AC_Action.java:878) at com.agile.hummingbird. API .executeEndAction( API .java:1874) at com.agile.hummingbird. API .handleAction( API .java:1614) at com.agile.hummingbird. API .directRequest( API .java:1089) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:890) at com.agile.hummingbird

I am running a stress test with 2 users, each making a request to the JSON API (which uses as storage ObjectDB) each 50 milliseconds. An API call might have between 1-4 db calls ... ) at com.fitbird.boundary. api .util.PlanAccessVerifier. (PlanAccessVerifier.java:40) at com.fitbird.boundary

;      at org.hibernate.validator. metadata .MetaConstraint. (MetaConstraint.java:75)         at org.hibernate.validator. metadata ... ; at org.hibernate.validator. metadata .BeanMetaDataImpl.initMethodConstraints(BeanMetaDataImpl.java:376

is actually 2 databases to seperate metadata used for searching and the data itself. So in total ... is reperesented by 2 databases under the covers - one for small metadata objects which are used ... which can be anything from 1k to 10mb. We've proved the benefits of keeping the metadata & data separate in past

.vereinsverwaltung.abrechnung. api .model.mitglied.MitgliedDebitorenKontoFragment) $1.qubletFRAGMENTMAP.get('com.lexware.vereinsverwaltung.abrechnung. api .model.mitglied.MitgliedDebitorenKontoFragment')).debitor=true)) AND ((((com.lexware.vereinsverwaltung.abrechnung. api .model.mitglied

.hummingbird. API .executeEndAction( API .java:1718) at com.agile.hummingbird. API .handleAction( API .java:1480) at com.agile.hummingbird. API .directRequest( API .java:1001) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:836) at com.agile.hummingbird.WebSocketServerListener.onWebSocketText

.hummingbird. API .handleGetContainer( API .java:2745) at com.agile.hummingbird. API .directRequest( API .java:802) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:630) at com.agile.hummingbird ... .java:163) at com.agile.hummingbird. API .handleGetContainer( API .java:2745) at com.agile.hummingbird. API

.hummingbirdcore. API .executeEndAction( API .java:3017)     at com.agile.hummingbirdcore. API .handleAction( API .java:2533)     at com.agile.hummingbirdcore. API .handleActionBulk( API .java:2133)     at com.agile.hummingbirdcore. API .directRequest( API .java:1695)   

output here.  I confirmed that the directory C:\Users\kwhittin\new_workspace_birt\. metadata ... _birt\. metadata \.plugins\org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb\db\META-INF ... \new_workspace_birt\. metadata \.plugins\org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb\db

.agile.hummingbirdcore. API .executeErrorAction( API .java:2940)     at com.agile.hummingbirdcore. API .handleAction( API .java:2418)     at com.agile.hummingbirdcore. API .directRequest( API .java:1621)     at com.agile.hummingbirdcore. API .handleWebSocketRequest( API

of the change. This API allows the application to notify the instance that a change was made to a field ... in this API , then the field marked dirty is the field declared by the most derived class. Transient

instance is not aware of the change. This API allows the application to notify the instance that a change

is not aware of the change. This API allows the application to notify the instance that a change

the default fetch group via the API does not affect the members defined by this category. Using this category

JDO Static Field in javax.jdo.FetchGroup DEFAULT For use with addCategory and removeCategory calls. This category includes members defined in the default fetch group in xml or annotations. Redefining the default fetch group via the API does not affect the members defined by this category. Using

is modified, then the persistent instance is not aware of the change. This API allows the application

, then the persistent instance is not aware of the change. This API allows the application to notify the instance