ObjectDB Database Search

make a difference for ObjectDB, but to remove this error / warning try: private @Basic(fetch=FetchType.EAGER) List flags; support Support

got follow Java Warning that tells me that Entity Class will be ignored. ../WEB-INF/lib/objectdb-2.6

;  blah..blah..    " Warning !"    "We strongly recommend that you avoid

:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) [ WARNING ] Failed

.base.bl.MessageService. warning (MessageService.java:117) btc_es BTC EmbeddedSystems These exceptions

truly bamboozled (hence this detailed forum posting). For the brave, be warned that for this type

Hi, i am using objectdb (version 2.6.8) in embedded mode. I deployed an .ear project in glassfish. When I attempt to call the database I get several exceptions. As an example consider the following short example: [#|2016-06-02T14:19:38.393+0200| WARNING |glassfish3.1.2|javax.enterprise.system.core

info and warn level) .     webel Dr Darren Kelly If the entity classes

has that changed?   dmoshal David Moshal There is a warning in the documentation (at the end

is enabled at DEBUG level. You can reduce the logging level of "type.loader" to WARNING to avoid

delete the database file each time. I get no errors nor warnings . Knut Hansson Knut Hansson Either use

, but if it fails it eventually proceeds silently without a lock (probably at least a warning has to be produced

that allows us to log the queries that cause such a warning ? hgzpincher Hans-Georg Zwicker Version 2.8

, WARNING , ERROR, AUDIT; @Override public String toString() { return this.name(); } } @Id

with no errors or warnings . To use ObjectDB outside a Java EE application server (starting build 2.6.2_02

it's really interesting: If we change the loggingLevel   from "fatal" to " warning

Fixed a bug in persisting objects with same ids in a class hierarchy in one transaction. Fixed a bug in using JDO Extent of a super class with shared primary key values in subclasses. Added a warning if a JDO SingleFieldIdentity class is used as a primary key field type.

, with: Increased threshold of examining combination, which fixes the "composite index not used" and a new warning

ways to improve the check to identify and warn against partial enhancement in future versions

Hey out there! Anybody experiencing this problem during a maven build while downloading from objectdb repository? This now occurs without any changes to a previously working pom.xml. [ WARNING ] Checksum validation failed, expected

that produces the warnings I am referring to: https://github.com/leblancjs/objectdb-jdo-duplicate-classes

Added support of enhancing classes with Java 11 dynamic constants. Added a warning if an expired activation is found in the configuration ( issue #2817 ) Fixed a bug in automatic conversion of embedded objects to collections.

= " warning " the code works. btc_es BTC EmbeddedSystems Your reports show that version 2.8.8_03 does

Added support of enhancing classes with Java 11 dynamic constants. Added a warning if an expired activation is found in the configuration ( issue #2817 ). Fixed the error message when required enhancement is missing ( issue #2828 ). Fixed recording of large transactions over 2GB in size ( issue