About Component

61-70 of 76Refresh
Result
1

ObjectDB version 2.6.1

Version 2.6.1 Added an option to disable temporary file deletion. Added support of using entity classes with missing dependent types. Added support of composite indexes with components of different lengths. Fixed a bug in reflection mode in detecting changes after flush (issue #1602). Fixed
Issue
1

Blocked by find

on that front. String ids are part of the app (and legacy components) so are unfortunately
Forum
1

composite index not used in query

, removing all unnecessary components. For example, try this query: SELECT count(a) FROM Action
Forum
1

Connection performace after upgrade to objectdb 2

, customers needs to load a component that depends on many odb file, the idea is to be able to dispaly data
Forum
1

disabling JDO in objectdb embedded mode

. But it is too large and unreadable) It seems to me that a "component" orders glassfish to load from
Forum
1

LEFT JOIN FETCH over empty embedded collection returns no results

component in the path. Please try build 2.5.0_06 that should change this behavior. FastModel
Forum
1

Measurement of the test coverage of enhanced classes

Hello, our Entities contains logic that we need to test. Therefore we have unit tests for all our entities. We build and test our components with Jenkins-CI. We want to test that what we release to our customers. Therefore we think we need to test the enhanced classes. But that distorts our test
Forum
1

Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found

the logging level of this ObjectDB component to ERROR:
Issue
1

NullPointer when accessing persistent field

=CascadeType.ALL, mappedBy="z_component") @MapKey(name="z_schemeName") private java.util.Map
Forum
1

ObjectDB within a resource adapter module and Java EE Connector Architecture

Has anybody managed to use ObjectDB in a resource adapter module in accordance with the Java EE Connector Architecture so that it may be packaged separately from (but used by components of) an EJB Module after the pattern of the classic EAR File structure as illustrated in the Java EE 7 tutorial in