ObjectDB Database Search

101-150 of 200 results

NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1

.Method.invoke(Method. java :601) org.jboss.as. ee .component.ManagedReferenceMethodInterceptorFactory ... .Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor. java :135) org.jboss.as. ee .component ... .processInvocation(WeavedInterceptor. java :53) org.jboss.as. ee .component.interceptors

JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception

.processInvocation(ManagedReferenceMethodInterceptorFactory. java :72) [jboss-as- ee -7.1.1.Final.jar:7.1.1 ... (WeavedInterceptor. java :53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as. ee .component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory. java :36) [jboss-as- ee -7.1

Glassfish 4 AbstractMethodError: com.objectdb.jpa.EMF.createEntityManager

Hi! I've been trying to get Glassfish 4 ( Java EE 7) work with ObjectDB the whole day. It seems to be an error. The same code (adapted to Java EE 6) works perfect in Glassfish 3.1.2.2. I attached ... , method: public void com.mirq.controller.UserC.findUser( java .lang.Long) WARNING:   javax.ejb

system exception occurred during an invocation on EJB GuestDao

" Java EE 6 JPA Tutorial - Maven Project" and imported it into eclipse: same problem ... version that implements JPA 2.0 with JPA 2.1 (in a newer Java EE ). support Support ... occurred during an invocation on EJB GuestDao, method: public java .util.List guest.GuestDao.getAllGuests

Cannot cast com.objectdb.jpa.Provider to PersistenceProvider

Hi! I'm trying to get ObjectDB 2.5.1_1 work with stable Glassfish 4 in a Java EE 7 NetBeans ... .jpa.JPADeployer prepare method SEVERE:   java .lang.ClassCastException: Cannot cast com.objectdb.jpa.Provider to javax.persistence.spi.PersistenceProvider at java .lang.Class.cast(Class. java

com.objectdb.o.InternalException: java.lang.NoClassDefFoundError: java/sql/Date

). Please report this error on http://www.objectdb.com/issue/new com.objectdb.o.InternalException: java .lang.NoClassDefFoundError: java /sql/Date java .lang.NoClassDefFoundError: java /sql/Date at objectdb/com.objectdb.o.VUT. (VUT. java :68) at objectdb/com.objectdb.o.RAT.l(RAT. java :106) at objectdb/com.objectdb.o.RTT

java.lang.NoClassDefFoundError: java/time/LocalDate

thread "main" [ObjectDB 2.8.6] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Client ... .objectdb.o.InternalException: java .lang.NoClassDefFoundError: java /time/LocalDate java .lang.NoClassDefFoundError: java /time/LocalDate at com.objectdb.o.VUT. (VUT. java :71) at com.objectdb.o.RAT.l(RAT

ObjectDB Overview

Features 100% pure Java Object-Oriented Database Management System (ODBMS). No proprietary API - managed only by standard Java APIs (JPA / JDO 2). Extremely fast - faster than any other JPA / JDO

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

.entity.Project com.greensoft.objectdb.test.mini.ejb.ExtProjectBuilder.buildProject( java .lang.String ... . java :2004) at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler. java :210) at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke

jakarta.persistence.metamodel.EntityType

of the managed type. Since: Jakarta Persistence (JPA) 1.0 Class getBindableJavaType () Return the Java type of the represented object. If the bindable type of the object is PLURAL_ATTRIBUTE , the Java element type is returned. If the bindable type is SINGULAR_ATTRIBUTE or ENTITY_TYPE , the Java type

jakarta.persistence.metamodel.IdentifiableType

of the managed type that corresponds to the specified name and Java element type. Inherited from ... and Java element type. Inherited from ManagedType Parameters: name - the name of the represented ... the managed type that corresponds to the specified name and Java element type. Inherited from ManagedType

jakarta.persistence.metamodel.ManagedType

of the managed type that corresponds to the specified name and Java element type. Parameters: name ... and Java element type. Parameters: name - the name of the represented attribute elementType - the element ... type that corresponds to the specified name and Java element type. Parameters: name - the name

jakarta.persistence.metamodel.EmbeddableType

to the specified name and Java element type. Inherited from ManagedType Parameters: name - the name ... the managed type that corresponds to the specified name and Java element type. Inherited from ... the managed type that corresponds to the specified name and Java element type. Inherited from

jakarta.persistence.metamodel.MappedSuperclassType

attribute of the managed type that corresponds to the specified name and Java element type. Inherited from ... name and Java element type. Inherited from ManagedType Parameters: name - the name ... -valued attribute declared by the managed type that corresponds to the specified name and Java element

Database Management Settings

. Activation codes are generated by running the Activator utility from the command line: $ java -cp objectdb

SELECT clause (JPQL / Criteria API)

performance and can sometimes reduce the amount of Java code needed. Note that query results

Storing JPA Entities

. getTransaction (). commit (); The Employee instance is constructed as an ordinary Java object

JPA Metamodel Types

Java type known to the persistence provider. Represents basic foundation types (primitives, wrappers

JPA Queries

The Criteria API provides a factory for defining queries programmatically using Java objects

JPA Named Queries

A named query is a statically defined query with a predefined, unchangeable query string. Using named queries instead of dynamic queries can improve code organization by separating JPQL query strings from Java code. This practice also enforces the use of query parameters instead of embedding

DELETE Queries in JPA/JPQL

+ an optional variable ObjectDB supports using the java .lang.Object class in queries as an extension

SQL Queries Annotations

Jakarta Persistence (JPA) provides a set of annotations to define and map native SQL queries when the standard Java Persistence Query Language (JPQL) is insufficient. While ObjectDB focuses on JPQL and ignores these annotations, they remain essential for applications interacting with relational

Where can I learn how to use ObjectDB?

The best source for learning ObjectDB is the ObjectDB Manual , which contains all the necessary information for using ObjectDB. The only required background is a good understanding of the Java language. Reading the manual and getting started with ObjectDB could be easier for developers with prior

Is ObjectDB better than Object Relational Mapping (ORM)?

is developed for an existing old relational database). By using the Java Persistence API (JPA

JPA Query API

Criteria API provides an alternative way to build dynamic queries. It uses Java objects that represent

JPA Metamodel and Graphs

to retrieve entity and attribute information by class or name, similar to the reflection API in Java

Database Schema Evolution

other conversion that is a valid casting operation in Java . Renaming (package, class, and Field

JPA Connections and Transactions

Working with the Java Persistence API (JPA) consists of using the following interfaces: Overview A connection to a database is represented by an EntityManager instance, which also provides methods for performing database operations. Many applications require multiple database connections

Running JPA Queries

like any other Java collection. For example, you can iterate over a result collection

JPA Relationships Annotations

Relationships define associations between entities. They are represented In Java code by attributes (persistent fields or properties) in persistent classes that hold a reference or a collection of references to other entities. Jakarta Persistence (JPA) provides annotations to configure

JPA ORM Mapping Annotations

java .util.Map when the type cannot be determined via generics. Specifies the mapping for the key column

JPA Criteria API Queries

Java objects that represent query elements. A major advantage of the Criteria API is that it enables

JPA Persistence Unit

;file to define a persistence unit. You can now define a persistence unit entirely in Java code

Database Explorer

line as follows: $ java -jar explorer.jar If explorer.jar is not in the current directory

jakarta.persistence.StoredProcedureQuery

to retrieve. Returns Integer. java .lang.Integer/MAX_VALUE if Query.setMaxResults was not applied ... . Deprecated: Newly-written code should use the date/time types defined in java .time . Since: Jakarta ... to a parameter of the query. Deprecated: Newly-written code should use the date/time types defined in java

jakarta.persistence.Basic

is any one of the following: a Java primitive type, or wrapper of a primitive type, String ... , or Year Date or Calendar , java .sql.Date , java .sql.Time , or java .sql.Timestamp , byte[] or Byte[] , char[] or Character[] , a Java enum type, or any other serializable type. The use of the Basic

jakarta.persistence.TemporalType

Jakarta Persistence (JPA) Enum jakarta.persistence.TemporalType java .lang.Object ∟ java .lang.Enum ... should use the date/time types defined in java .time . Since: Jakarta Persistence (JPA) 1.0 The JPA Persistable Types article explains how to use TemporalType . Enum Constants DATE Map as java .sql.Date

jakarta.persistence.EntityNotFoundException

Jakarta Persistence (JPA) Class jakarta.persistence.EntityNotFoundException java .lang.Object ∟ java .lang.Throwable ∟ java .lang.Exception ∟ java .lang.RuntimeException ∟ jakarta.persistence ... ) EntityManager.refresh(Object, java .util.Map) EntityManager.refresh(Object, LockModeType, java .util.Map

jakarta.persistence.EnumType

Jakarta Persistence (JPA) Enum jakarta.persistence.EnumType java .lang.Object ∟ java .lang.Enum ... how a persistent property or field whose type is a Java enum type should be persisted. See Also: Enumerated ... . The ordinal value of an enum instance with no EnumeratedValue field is the value of its Enum. java .lang.Enum

Spring MVC and JPA Tutorial

This tutorial demonstrates how to create and run a full Java Spring MVC (Model View Controller) web application using Tomcat (or GlassFish), JPA, ObjectDB and Maven. The demo web application manages a basic guestbook page. Every visitor can sign the guestbook by filling a simple form. All visitors

Step 4: Add a Controller Class

In this step we will add a Spring Controller to manage guestbook web requests: Open the [New Java Class] dialog box by right clicking the guest package node (in the [Package Explorer] window) and selecting  New Class . The package name should be  guest . Enter  GuestController as

Step 3: Add a Context Listener Class

Other... Web Listener and clicking Next . The Java package name should be guest. Enter GuestListener as

Step 1: Create a Maven Web Project

.2 enhance process-classes java com.objectdb.Enhancer guest.Guest org.mortbay.jetty maven-jetty

Step 3: Add a Main Class

tutorial; import javax.persistence.*; import java .util.*; public class Main { public static void main

Step 3: Add a Main Class

.persistence.*; import java .util.*; public class Main { public static void main(String[] args) { // Open

JPA Web Application Tutorial

This tutorial demonstrates how to create and run a database driven Java web application using Tomcat 6, ObjectDB and JPA. The demo web application manages a basic guestbook page. Every visitor can sign the guestbook by filling a simple form. The visitors that have already signed are listed

Step 3: Add a Context Listener Class

exactly that case sensitive class name. The Java package name should be guest. Click Finish

Getting Started with JPA - Eclipse Project

Eclipse: Right click the project node and select Run As Java Application . Select Main - point and click OK .

Step 1: Create a Web Project

We start by creating a new NetBeans Web Application Project: Open the [New Project] dialog box, e.g. by using File New Project... Select Java Web Web Application and click Next . Choose a Project Name (e.g. Guestbook ) and click Next . Select Apache Tomcat 6 as the Server. Note

Step 7: Run the Spring Web App

enabled without specifying a Java agent. This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual .