ObjectDB Database Search

, using an older version of GraphQL (in which this is a warning rather than an error), or disabling ... reflection mode? Try the following configuration : You will get the indication as a warning . support

. If StringIndentity is not to be used with ObjectDB that way, then some sort of warning message would be great to help avoid making the same mistake I did. CBE CBE A warning was added in build 2.7.3_06

; Resulting error: [11:47:18]: [com.rbccm.felix.server:integration-test] 11:47:18,588 main WARN

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

hash; } @Override public boolean equals(Object object) { // TODO: Warning - this method won't work in

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

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

file OK. However, even when duplicating the orm.xml, a different error pops up: WARNING : DTX5014

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

order of values in the enum all the way. support Support See also the warning (regarding using enum

to ignore this mismatch (we just have to comment a validity check), but the idea is to warn against mixing

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

detected and saved. Am I doing something wrong that may stop working without warning ? kjkrum Kevin

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

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

of this message may change from WARNING to DEBUG in the future. support Support I understand. Thank you. zmirc Mircea Chirac

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

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

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

your suggestion of catching these exceptions. Warning messages will be logged. support Support

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

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

out the correct path or argument line to use. i can see a warning in the odb log file about my entity not

log is as follows:   WARNING : DTX5014: Caught exception in beforeCompletion() callback

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

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

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

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

it. The Glassfish3.01 log stacktrace is: WARNING : StandardWrapperValve[Faces Servlet]: PWC1406: Servlet.service

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

..   Alex quasado Alexander Adam I think that a missing objectdb.conf causes a warning but not

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

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.

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

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.

level JDO sequence using getSequence ( issue #1074 ). Fixed false Doctor warnings when updating

Added OSGi support. Added support of MEMBER OF for inverse (mapped by) collections. Changed logging of incomplete recovery records from WARNING to TRACE  ( issue #565 ). Changed main configuration elements from required to optional. Fixed the "Negative snapshot user count" bug ( issue #556

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