28 | Deploy ObjectDB in WildFly 10 get an error: 017-10-23 09:23:31,715 INFO [org.jboss.as.jpa] WFLYJPA0002: Read persistence.xml ... to process phase FIRST_MODULE_USE of deployment "omd-in-memory-db.jar" at org.jboss.as.server ... : PersistenceProvider 'com.objectdb.jpa.Provider' not found at org.jboss.as.jpa.processor |
25 | Performance problemHi, we have a strange performance problem with ObjectDB 2.5.3_01 and JBoss 7.1.1 ... one running JBOSS and other running ObjectDB. - CPU utilization of JBOSS server is max 5-10% (per core) - CPU utilization of JBOSS server is 80-150% (this is per core) Now is the interesting |
5 | SELECT clause (JPQL / Criteria API), the following query returns country names as String instances, rather than Country objects: SELECT c.name FROM Country AS c Using path expressions, such as c.name, in query results is referred to as ... results. The results of the above query are received as a list of String values: TypedQuery<String |
4 | FROM clause (JPQL / Criteria API) over all the Country objects in the database: SELECT c FROM Country AS c The AS keyword is optional, and the same query can also be written as follows: SELECT c FROM Country c By default, the name ... pair of countries that do not share a border, returning as results only neighboring countries |
4 | objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active' entity wiring methods: As simplified here to demonstrate the problem: @Singleton @Startup public ... one wishes to build, but it's not an ideal solution. It works (for now) as a workaround ... a transaction such as buildProject() causes with ObjectDB 2.6.9_06 the same error as initially reported |
4 | JPA Persistable Types can be stored in the database directly. Other persistable types can be embedded in entity classes as fields ... a class as an entity is to mark it with the Entity annotation: import javax.persistence.Entity ... user defined class (but not system classes, such as ArrayList) and implement any interface |
0 | [ODB1] Chapter 8 - ObjectDB Server. More details on server configuration and operation are provided later in this chapter. The Server as a Java program You can run the server as a Java program from the command line, as so: > java -cp <OBJECTDB ... Running the ObjectDB server edition without command line arguments displays a usage message, as shown |
0 | [ODB1] Chapter 4 - JDO Metadata) and classes B, C and D (in package test), as persistent. In addition to the required name attribute, a <class ... if it is also persistent. In the above metadata example, class C is probably defined as a subclass of class B ... declaring a persistent class as a subclass of a non persistent class. Of course, in that case the fields |
0 | [ODB1] Chapter 3 - Persistent Classes. The JDO specification refers to persistent classes as persistence capable classes. 3.1 Persistent ... and can have only transient objects as instances. To become persistent, a class has to: be declared ... automatically, as explained in section 3.3. ObjectDB's JDO Enhancer also adds a no-arg constructor |
0 | [ODB1] Chapter 9 - ObjectDB Explorer databases. 9.1 Running the Explorer The Explorer is a pure Java GUI application. It is shipped as ... can be specified as an argument to explorer.exe during startup. For instance: > explorer.exe ... queries in the Explorer, as discussed below. Finally, the "Thread" window, unlike |
