Internal Website Search

Hi, I am using JDO access to the database with the persistence defined in package.jdo XML metadata files. In those metadata files I have few persistence-capable classes which had extents in ObjectDB ... and own OID) in those few peristence-capable ones. Example of JDO metadata :        

API .   Tested JPA 2.0 providers    * Hibernate 3.6.1 - PASS. Minimum version 3.6.1 - older versions have a bug in the Criteria API implementation which prevents correct negation ... ;  * DataNucleus 2.2.2 - FAIL. Was not able to create even a simple query with Criteria API .  

Hi! I am trying to use the Enhancement API from within my application like this: com.objectdb.Enhancer.enhance("my.package.Foo"); However, I get the following NullPointerException: [ObjectDB 2.7.1 ... above). I'm not sure what is happening, the class exists and trying the API with a non-existent class

Hi.   Is Java 8 new DateTime API supported natively or through Converters in the newest versions of objectdb? If not, can we expect this feature in the next releases?   Best regards and congratulations on this awesome database.  Amsterdam Amsterdam Luís de Lima Filho It is not

Customer asked during opened ObjectDb connection (ODB location A) to stop writing and continue to another ODB file (Location B). Does exist some API to achieve that? What is a possible solution? Harman Alexander Golyshkin You have to close the database in location A, copy it from location

Is there an API to get the current version of ObjectDB that's being used? This would be very handy to have, because it is somewhat difficult to know what version of the ObjectDB you are currently using since the objectdb.jar filename remains the same for all versions (which is not a bad thing by

fetch doi. metadata metadata left join fetch metadata .titles titles left join fetch metadata .creators creators left join fetch metadata .descriptions descriptions left join fetch metadata .publishers publishers left join fetch metadata .contributors contributors left join fetch metadata .dates dates left

Hi, I am about to update the JDO metadata in the package.jdo files after moving from ObjectDB 1 to 2. However I found that there is no complete description or guide how the XML metadata should look ... description of XML metadata for ObjectDB ver2 using JDO which I did not find? 2. Is the combined

ObjectDB Software develops, markets and supports the ObjectDB Object-Oriented Database Management System (ODBMS). ObjectDB Software is the market leader in providing a very high performance persistence solution for Java, based on the Java Persistence API (JPA) and the Java Data Objects (JDO

/slf4j- api -1.6.4.jar, URLEntry : file:/usr/local/glassfish/glassfish/domains/dex/applications ... .0-SNAPSHOT/lib/javaee- api -6.0.jar, URLEntry : file:/usr/local/glassfish/glassfish/domains/dex ... - org.glassfish.internal. api .DelegatingClassLoader@43de6a4f AT Thu Jun 02 14:19:14 CEST 2016 BY :java

with the Persistence api : EntityManagerFactory emf = Persistence.createEntitManagerFactory("project.odb"); //this set ... -classes to false. The Metamodel API still returns the empty set when 'getEntities()' is invoked ... the Metamodel API (storing objects, etc)? Does it work? support Support So I changed the persistence

. Within the persistence context, the entity instances and their lifecycle are managed. The EntityManager API is used ... ). Parameters: name - the name of a query defined in metadata Return: the new query instance Throws ... metadata resultClass - the type of the query result Return: the new query instance Throws

have long been a fan of JDO as it's a hugely easer API and gets work done with a lot less metadata .  ... and a test will be needed. Regarding JPA/JDO, when using ObjectDB no need to use much metadata in either of them, so you can stay with JPA and just remove the ORM metadata when switching to ObjectDB

- if the query is found not to be a Java Persistence query language SELECT query or a Criteria API ... of the parameter as registered or specified in metadata Return: the result that is passed ... metadata type - type of the parameter mode - parameter mode Return: the same query instance

JDO 3 introduces the ability to specify and query metadata of persistable types dynamically. ObjectDB 2 supports specifying metadata by: JPA XML Mapping Metadata JPA Annotations JDO XML Metadata (e.g. package.jdo) JDO Annotations All these methods are static, i.e. the metadata has to be provided

APIs can be overridden. Information that is overridden does not affect the named query as registered ... of the same name has been previously defined, either statically via metadata or via this method, that query ... of the specified type to allow access to the provider-specific API . If the provider's EntityManagerFactory

is executed, information that can be set by means of the query APIs can be overridden. Information ... , either statically via metadata or via this method, that query definition is replaced. Parameters

Hello, I'm using the Java Persistence API (JPA) in a library to not lock myself in to using ... . To use the @Index annotation, I had to add a dependency to the JDO API version 3.1 (old link: https://mvnrepository.com/artifact/javax.jdo/jdo- api /3.1). The code works just fine, but when I use

and should not be bound to specific entity classes and persistent fields. Therefore, an API for accessing ... database with no original classes: Use the Metamodel API to find details on the entity classes in ... exists in the database and missing from the classpath.  Use Java reflection API with information

The JPA Criteria API supports dynamic definition of JPQL queries using CriteriaBuilder as ... Criteria API in expected in future versions. support Support   Implementation of the JPA Criteria Query API was just added to ObjectDB in version 2.1.1_01. It will be officially supported

One of the new features of JDO 3 is a standard API for enhancement. Currently ObjectDB implements its own enhancement API . support Support

Hello, This is getting really frustrating sorry but we're close before delivering our app to our customer and went against a show-stopper again. We're building a simple query with the criteria api ... ; } }; Create Selection Query (Critera- API ) from * TestEntity and add WHERE class

the sorted results. However, running this with the criteria API produces this error: Caused by: com

Issue with TYPE expression in Criteria API

criteria api / embedded objects / where order

- the name of a query defined in metadata resultClass - the type of the query result Return

JPA Annotation Attribute in javax.persistence.NamedStoredProcedureQuery String[] resultSetMappings default {} The names of one or more result set mappings, as defined in metadata . Since: JPA 2.1

more result set mappings, as defined in metadata . Since: JPA 2.1

JPA Annotation Attribute in javax.persistence.NamedNativeQuery String resultSetMapping default "" The name of a SqlResultSetMapping , as defined in metadata . Since: JPA 1.0

resultSetMapping default "" The name of a SqlResultSetMapping , as defined in metadata . Since: JPA 1.0

this annotation in the metadata . Example: Query q = em.createNativeQuery( "SELECT o.id AS order_id, " + "o

of the parameter as registered or specified in metadata type - type of the parameter mode - parameter mode Return: the same query instance Since: JPA 2.1

registered or specified in metadata Return: the result that is passed back through the parameter

of type Object[]. Parameters: name - name assigned to the stored procedure query in metadata Return

JPA Method in javax.persistence.EntityManager Query createNamedQuery (   String name ) Create an instance of Query for executing a named query (in the Java Persistence query language or in native SQL). Parameters: name - the name of a query defined in metadata Return: the new query

that is specific to top-level queries. Since: JPA 2.0 The JPA Criteria API Queries article explains how to use ... : Applications using the string-based API may need to specify the type of the select item when it results

metadata for any PersistenceCapable class that has registered with JDOImplHelper . This is dangerous in that metadata information (possibly confidential) normally unavailable would be accessible to malicious code. manageMetadata This allows managing metadata for any PersistenceCapable class

is a helper class for JDO implementations. It contains methods to register metadata for persistence-capable ... Since: JDO 1.0 void unregisterClass (Class pcClass) Unregister metadata by class. This method unregisters the specified class. Any further attempt to get metadata for the specified class will result in

a concrete or abstract class that is declared in the metadata . Return: the created instance Since: JDO 2.0 ... metadata . Parameters: cls - the Class of candidate instances queryName - the name of the query to look up in metadata Return: the new Query Since: JDO 1.0 Object newObjectIdInstance (Class pcClass

JDO Method in javax.jdo.spi.JDOImplHelper void unregisterClasses (   ClassLoader cl ) Unregister metadata by class loader. This method unregisters all registered PersistenceCapable classes loaded by the specified class loader. Any attempt to get metadata for unregistered classes

JDO Method in javax.jdo.spi.JDOImplHelper void unregisterClass (   Class pcClass ) Unregister metadata by class. This method unregisters the specified class. Any further attempt to get metadata for the specified class will result in a JDOFatalUserException . Parameters: pcClass - the PersistenceCapable class to be unregistered. Since: JDO 1.0

query. The query name given must be the name of a query defined in metadata . Parameters: cls - the Class of candidate instances queryName - the name of the query to look up in metadata Return: the new Query Since: JDO 1.0

;   PersistenceCapable pc ) Register metadata by class. The registration will be done in

or abstract class that is declared in the metadata . Return: the created instance Since: JDO 2.0

JDO Interface Sequence Implementations of this interface can be used to obtain sequences. The behavior with regard to the transaction and rollover behavior are defined in the metadata . Since: JDO 2.0 Public Methods void allocate (int additional) Provides a hint to the implementation

JDO Method in javax.jdo.Query void setUnmodifiable () The unmodifiable flag, when set, disallows further modification of the query, except for specifying the range, result class, and ignoreCache option. The unmodifiable flag can also be set in metadata . Since: JDO 2.0

, except for specifying the range, result class, and ignoreCache option. The unmodifiable flag can also be set in metadata . Since: JDO 2.0

- a RegisterClassEvent instance describing the registered class plus metadata . Since: JDO 1.0

JDO Method in javax.jdo.spi.RegisterClassListener void registerClass (    RegisterClassEvent  event ) This method gets called when a persistence-capable class is registered. Parameters: event - a RegisterClassEvent instance describing the registered class plus metadata . Since: JDO 1.0

, and the array is modified, then the persistent instance is not aware of the change. This API ... the same field, and if the package and class name are not provided by the parameter in this API