Home » Search

About not

11-20 of 200Refresh
Manual
15

Collections in JPQL and Criteria Queries

. as path expressions - in navigation to persistent collection fields. IS [NOT] EMPTY The IS [NOT] EMPTY operator checks whether a specified collection is empty or not. For example: c.languages IS EMPTY is TRUE if the collection is empty and FALSE otherwise. c.languages IS NOT EMPTY is FALSE
Forum
14

Pre-detach loading: retrieval by navigation not working in if statement

: objectdb.temp.no-detach NOT USED This problems only seems to occur in my large web application. I know ... application parallel to the large web application, but the problem does not happen in the smaller web ... , which is a "one size fits all" approach, does not meet my needs for all situations. I can configure an entity
Manual
13

Comparison in JPQL and Criteria API

Equal To >= >= Equal = == Not Equal <> != The two sets differ in the Equal and the Not Equal ... . When both operands are not NULL (not shown in the table) the operator is evaluated to either TRUE or FALSE ... and expressions that include an unknown value are evaluated as unknown, i.e. to NULL. IS [NOT] NULL
Forum
13

JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception

);   if ( type == null )     System.out.println( "ManagedType Guest not found"  );   // NamedQuery does not work   // TypedQuery query = this.em.createNamedQuery( "Guest.getAll", Guest.class ... ="select g from guest.Guest g order by g.name" ) } ) ... // NamedQuery does not work // TypedQuery
Forum
13

Apache Tomee 1.5.2: Failed to use JTA (TransactionManager is not found)

", I can deploy, but not with JTA. May 20, 2013 11:50:32 PM org.apache.tomee.catalina ... (TransactionManager is not found): com.objectdb.o._PersistenceException: Failed to use JTA (TransactionManager is not found) at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler
Issue
13

Remove of an entry from a @OneToMany collection is not possible if the enhancer is disabled

Hello! When the JPA entities are not enhanced the removal of an entry from a @OneToMany collection is not possible. The following java code demonstrates the problem. The statement parentEntity.getChildEntityContainer().remove("01"); does not work correctly with not enhanced JPA entities
Forum
13

java 8 LocalDateTime is not working in query

: SELECT t FROM Test t New Java 8 date/time types are not supported by JPA yet. I don't want to sound rude, but if you want to play the JPA compatibility card here, it is not quite working: In JPA ... , and on the other side it is not compatible enough. I would appreciate any constructive thoughts concerning
Result
13

Eclipse Public License - v 1.0

anyone acting on such Contributor's behalf. Contributions do not include additions to the Program ... under their own license agreement, and (ii) are not derivative works of the Program. "Contributor" means any person or ... to be covered by the Licensed Patents. The patent license shall not apply to any other combinations
Forum
13

@Convert is not supported?

;   I've wrote a test on this, and seems that my Converters methods are not executed at all (like ... _Converter )  @Converter / @Convert are new in JPA 2.1 and ObjectDB support of JPA 2.1 is not complete ... for other purposes I'm not aware of), I have an Entity which has not much instances in database
Forum
13

em.flush(); em.clear(); loosing data and not persisting managed objects

I'm having trouble with flush() and clear() in a loop inside a transaction not persisting modified ... sutable for the new DRCS. I chose JPA since it was not specific to a peticular database. I chose to try ... very well and have a sequencial integer as the primary key. But of all the file/tables 3 or 4 or them do not