12 | Issue deploying J6EE/Eclipse/Glassfish example to TomEE 1.5.1. It seems to be hardcoded to assume it is being deployed into JBoss AS: ....snip.... Caused by: com.objectdb.o ... : javax.naming.NameNotFoundException: Name [jboss/TransactionSynchronizationRegistry] is not bound in this Context. Unable to find [jboss]. at org.apache.naming.NamingContext.lookup(NamingContext.java |
12 | A lot of ENT and SIV instances which are not cleared by GC(EjbInvocation.java:582) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke ... (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.weld.injection ... ) at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.preDestroy |
2 | CRUD Database Operations with JPA.getTransaction().commit(); Operations that modify the content of the database (such as storing new objects) require an active transaction. In the example above, every Point object is first constructed as an ordinary Java object. It then becomes associated with an EntityManager and with its transaction (as |
2 | Entity Management Settings the persistence context of the EntityManager (which serves as a first level cache). The valid values ... "false") specifies if lazy loading of entity objects content is enabled. Instantiating entity objects as ... (whose value is "true" or "false") specifies if serialization should be used as a fallback persisting |
2 | Auto Generated Values this annotation for non-key numeric persistent fields as well. Several different value generation strategies can be used as explained below. The Auto Strategy ObjectDB maintains a special global ... for entity objects with no primary key fields defined (as explained in the previous section). The same |
2 | JPA Primary Key key cannot be modified. It represents the entity object as long as it exists in the database. As ... of other persistable types are always stored as part of their containing entity objects and do not ... automatically : } The @Id annotation marks a field as a primary key field. When a primary key field |
2 | Comparison in JPQL and Criteria API ObjectDB supports two sets of comparison operators, as shown in the following table: Set 1 - JPQL ... and expressions that include an unknown value are evaluated as unknown, i.e. to NULL. IS [NOT] NULL ... have exactly the same content. ObjectDB supports comparison of any two values that belong to the same group as |
2 | JPA Query Structure (JPQL / Criteria) rather than just field values from database tables, as with SQL. That makes JPQL more object oriented friendly and easier to use in Java. JPQL Query Structure As with SQL, a JPQL SELECT query also consists ... elements such as names of entity classes and persistent fields, which are case sensitive. In |
0 | Step 2: Entity Class and Persistence Unit as Folder Name and click Finish. Open the [New Java Class] dialog box, e.g. by right clicking the new source directory node (in the [Package Explorer] window) and selecting New > Class. Enter guest as the package name - use exactly that case sensitive package name. Enter Guest as the class name |
0 | Step 2: Entity Class and Persistence Unit) and selecting New > Class. Enter guest as the package name - use exactly that case sensitive package name. Enter Guest as the class name - use exactly that case sensitive class name. Click Finish ... and clicking Next). Select the project src folder as a parent folder, enter META-INF as a new folder |
