Internal Website Search

;() { @Override protected void updateItem(String item, boolean empty) { if(item != null ... empty) { if(item != null) { setText(item); setAlignment(Pos.CENTER ... ;() { @Override protected void updateItem(String item, boolean empty) { if(item != null

manager factory is obtained, the Metamodel is empty - none of the entities referenced in ... .createEntitManagerFactory("project.odb"); //this set is alwasy empty with ObjectDB Set<EntityType> ... > The Metamodel API still returns the empty set when 'getEntities()' is invoked.

if getObjectsById() is called with an empty collection? carr.onstott Carr Onstott There are no known issues with this method. If you pass an empty collection the method should return an empty

part of the test? Or should it be empty? Pretty much I want a unit test that shows the locationlist coming back empty, and then someway of calling so that it comes back populated. I'm uncertain now ... to initialize the field with an empty lazy proxy collection (because your application uses JPA property

>   dmoshal David Moshal You can disable the L2 cache (or empty it with evict) and empty the EntityManager (L1) cache ... > You can empty the L2 cache or remove

, collection operators and methods (IS EMPTY, SIZE, MEMBER OF, IN) are currently not supported for mapped by ... ; //    "SELECT a FROM A a WHERE a.list IS EMPTY");        ... ;  // SELECT a FROM A a WHERE a.list IS NOT EMPTY         List

via a querying @EJB gives many fields null (and not even empty, I mean truly null). In ... > In all cases lists that are given in the explored database either empty or populated are served ... it (the lists load non-null, either as empty or correctly populated). This seems to imply

> On further investigation it looks like this may be related to the initial empty state of the database. I inserted ... (therefore, with an almost empty database this is more likely to happen frequently). empty but this would be a bit messy as it is defined by UserException + message text.

problem. In this case we weren't affected as the dbs were empty anyway but I'm a bit worried ... every time you are trying to open that empty database with its associated odb$ file? support ... file exists but it is empty. Build 2.3.7_09 should fix this issue. Thank

the value for this field or property (if any). If customValueStrategy is non-empty, then valueStrategy