Internal Website Search

101-150 of 200 results

Cast exception?

Flying Banana Jiacong Xu Since it is a casting from a type to itself it probably fails ... the query? If so how can I work around it? Flying Banana Jiacong Xu You do cast implicitly by using ... is using. What are the ways to go around this? Flying Banana Jiacong Xu This seems to be a partial stack

Unexpected internal exception during set field of an Embeddable to null

to be smaller. During enhancement of the  SignalValueImpl class field originalValue was the 4th field. Assuming that there may have been a schema change since that enhancement rebuilding the project and enhancing all classes again may solve the issue. If it doesn't please upload the embedded

PersistenceException: Failed to locate field

may be thrown if you mix old and new enhancement . Please make sure that after the change you only use a clean build of your application with fresh enhancement . support Support Thanks, though I've been using this enhancement for ages (I think it's actually means no enhancement , serialization only): dmoshal

Embedding ObjectDB on server application

; Flying Banana Jiacong Xu The error message that you get may indicate that objectdb.jar is not found in ... (ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:722)   Flying Banana Jiacong Xu It looks ... somehow. I came up with a workaround and it's now working! Thanks :) Flying Banana Jiacong Xu It seems like

NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1

. galandor Orlov Sergey This exception indicates a missing enhancement , i.e. City is enhanced but its super class AbstractMethod is not enhanced . It is indeed weird that the problem is only with City ... and then redeployment solve the problem. You may also try using build time enhancement

Unable to store AtomicInteger

ObjectDB 2.6. Is this a bug? Flying Banana Jiacong Xu Serialization is disabled by default ... , then there shouldn't be a problem, right?) Flying Banana Jiacong Xu You may either use serialization or the PostLoad solution in this case. support Support

evictAll() behavior

that your persistence capable (entity) classes are not enhanced . ObjectDB supports working with no enhancement as an extension to JDO - but it is less efficient and has some limitations. For example, strong ... cannot be evicted. If your classes are not enhanced - enhancing them could solve the problem without any

PostUpdate on array changes

the system complains: [ObjectDB 2.8.0_04] javax.persistence.PersistenceException Type au.Person is not enhanced ( enhance the type or enable reflection)  (error 304)     at com.objectdb.jpa ... getting an error regarding enhancement - is this because I'm using openjdk version "1.8.0_212

Entity is not related to ObjectDB, but i get exception from ObjectDB

java:jboss/datasources/PG Perhaps this is because of Enhancer , how can we disable it in this case ... . 

Looking forward to your response
 galandor Orlov Sergey This could happen due to partial enhancement , i.e. all the project is enhanced , but then specific classes are compiled again without enhancement

JBoss 7 startup fails

the enhancer (error 108) 13:49:37,705 ERROR [stderr] (MSC service thread 1-3) com.objectdb.o.UserException: Package guest is not found by the enhancer 13:49:37,706 ERROR [stderr] (MSC service thread 1 ... .o.JEN.k(JEN.java:90) 13:49:37,708 ERROR [stderr] (MSC service thread 1-3) at com.objectdb. Enhancer

Failed to generate dynamic type

Hi  I was trying to enhance some of my classes and I got an error :  Failed to generate ... advance b bolo Boguslaw Fraszko one more thing ....  : how to increase Enhancer log level ??   ... there is output from enhancer [ObjectDB 2.0] 3 persistable types have been enhanced : test.MyEntity1 test.MyEntity2

AbstractMethodError ... __odbSetTracker(Lcom/objectdb/spi/Tracker;)V

.EMImpl.find(EMImpl.java:518) ~[na:na] btc_es BTC EmbeddedSystems It may indicate a partial enhancement ... and enhancement of all the classes. support Support Good morning, Without enhancing any entities, we get the error mentioned in first post. When we enhance all entities, we get the following error instead: java

javax.jdo.JDOUserException Failed to locate field field exampleField using reflection (error 363)

, that we have properly enhanced classes although it seems to me, that we  aren't using a best practise solution ... it we are using following code: String allString = getAllPackagesAsString(); Enhancer . enhance (allString); Output of enhancement before running the test was: [ObjectDB 2.8.3_05 Enhancer ] 553 persistable types

Entity Update - Is the documentation up to date?

. These changes are detected if your classes are not enhanced . If your classes are enhanced ... to elements that are not detected in enhanced classes, correct? If a class variable is assigned a new value ... a (potentially identical) new value? kjkrum Kevin The behavior is different for enhanced classes and non

Insert time increases as db grows.

one entity have index on String column. Entities are not enhanced and inserts are committed in a separate ... ? 4410 Arsenii With enhanced classes you may get much better performance. Enhancement is very easy. For example, you can apply enhancement by: java -javaagent:c:\objectdb\bin\objectdb.jar

OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011)

that creates my application (with ObjectDB Enhanced classes) but my application fails with the error ... and activations in recent versions. Please make sure that your classes are OEM enhanced . See this forum thread . support Support Thank you for the link to the class enhancing confirmation checking code. 

Determining if Persistable Classes Have Trial Limitation

this used to work was that the Enhancer would not Enhance or sign the specified persistable classes ... .6 Enhancer ] 7 persistable types have been enhance How can I tell if a build does NOT occur ... activation code is available the message should be: [ObjectDB 2.7.6 OEM Enhancer ] rather than 

Objectdb Doctor

, which are not stored but rather computed on the fly by executing automatic queries). ObjectDB Doctor

Duplicate Entity class names causes Exception in Query

our JP QL fly ! JFK John Francis Sorry it appears this is an intermittent exception   I

Query vs Extent for retrieving data

from the database on the fly , is available only when the PersistenceManager is open

Extended mapping-definitions

classes, by generating them on the fly (there are several Java libraries that can do that). support Support

Opensource ObjectDB

there are no plans to open source ObjectDB. support Support Would be great if that 10 entity class limit is raised, even by a bit :P Flying Banana Jiacong Xu

Feature Request: Improved ObjectDB Explorer

here for discussion before submitting a ticket. What do you think? Flying Banana Jiacong Xu I agree

A few questions on object database design

? Flying Banana Jiacong Xu There are no strict rules because the optimal design depends on too many

Entity factory - best practices

at the same time? Flying Banana Jiacong Xu Creating multiple EntityManagerFactory instances is thread safe

objectdb (licensed) + github action error

on the fly for each upgrade. Any idea how we can resolve it? Thanks in advance for your help.   jon

Best practise loading big data

? maybe you can use rollback or clear instead of commit? Do you always use only enhanced classes? With enhanced classes ObjectDB is not expected to hold strong references (which prevents garbage ... then we can do that instead. Thanks for this hint! Yes, only enhanced classes are used in this example

Internal objectdb exception when using different language on a machine

was not enhanced and caused the exceptions above. Although the enhancement check was activated: the enhancement check does not throw an objectdb exception. Have you an idea why the enhancement check does ... that you found the cause and thank you for the update.  Have you an idea why the enhancement check

Exception in thread "main" java.lang.NoSuchFieldError: __odbTracker

Hi   there is something wrong with enhancement process I got that class was succesfully processed, log has size 0, enhancer is from build objectdb-2.2.8_08 and during object creation when some ... Tomasz Wozniak This might be the result of an incomplete enhancement - i.e. Network extends

Error during closing an entity manager

btc_es BTC EmbeddedSystems We have found a workaround. We have just enhanced the entities and then it works as intended. But why this case does not perform without enhanced entities? btc_es BTC EmbeddedSystems The exception may be due to having partial enhancement . Mixing enhanced entity classes

javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName

Enhancer modifies the names of persistent property  get and set methods by adding __odbHidden ... that. If this doesn't help maybe the Enhancer has to move the annotations to the proxy methods ... is not anywhere in the classpath. You are not using classes that have been enhanced by an older

Unexpected Exception during commit

; em.close();     I also tried upgrading to 2.2.9_05. Now when I try to enhance I ... . Enhancer . enhance ( Enhancer .java:66) at com.objectdb. Enhancer . enhance ( Enhancer .java:87) at com ... ( enhancer ) exception in build 2.2.5_05 is caused by using the new build with an older configuration file

Unexpected Exception (java.lang.NullPointerException: Cannot invoke "com.objectdb.o.ORS.Z9())

this check is not needed when entity classes are enhanced , so enhancing the class may solve the issue. Note that mixing enhanced and non- enhanced classes is not supported and may cause various issues, so double check that all your entity classes are enhanced . Something else to check is that all objects

Feature Request: Adding map entries to DB in Explorer

Currently, collections can be edited but maps cannot be edited. For a database model that has a lot of static data that need to be entered into the database on multiple edits this presents as an inconvenience. It would be great, therefore, if we can edit maps straight from the explorer. Flying Banana Jiacong Xu

queries under 2.7.6_4 significantly slower than under 2.7.6

we have queries like the above that are entered by customers on the fly , no chance to use hints

database corrupt

infrastructure. We could gather more information if needed. the 'on the fly ' Doctor would be great

javax.jdo.listener.ClearCallback

the runtime environment should be cleared. This method is not modified by the enhancer . Since: JDO 2.0

ClearCallback.jdoPreClear() - JDO Method

JDO Method in javax.jdo.listener.ClearCallback void jdoPreClear () Called before the values in the instance are cleared. Transient fields should be cleared in this method. Associations between this instance and others in the runtime environment should be cleared. This method is not modified by the enhancer . Since: JDO 2.0

javax.jdo.listener.ClearLifecycleListener

and others in the runtime environment should be cleared. This method is not modified by the enhancer

ClearLifecycleListener.preClear(event) - JDO Method

modified by the enhancer , so access to fields is not mediated. Parameters: event - the clear event. Since: JDO 2.0

javax.jdo.listener.DeleteCallback

is modified by the enhancer so that fields referenced can be used in the business logic of the method. Since: JDO 2.0

DeleteCallback.jdoPreDelete() - JDO Method

after this call are disallowed. This method is modified by the enhancer so that fields referenced can be used in the business logic of the method. Since: JDO 2.0

javax.jdo.listener.LoadCallback

JDO Interface LoadCallback This interface is used to notify instances of load events. Since: JDO 2.0 Public Methods void jdoPostLoad () Called after the values are loaded from the data store into this instance. This method is not modified by the enhancer . Derived fields should be initialized in

LoadCallback.jdoPostLoad() - JDO Method

JDO Method in javax.jdo.listener.LoadCallback void jdoPostLoad () Called after the values are loaded from the data store into this instance. This method is not modified by the enhancer . Derived fields should be initialized in this method. The context in which this call is made does not allow

javax.jdo.listener.StoreCallback

should be updated in this method. This method is modified by the enhancer so that changes to persistent

StoreCallback.jdoPreStore() - JDO Method

JDO Method in javax.jdo.listener.StoreCallback void jdoPreStore () Called before the values are stored from this instance to the data store. Data store fields that might have been affected by modified non-persistent fields should be updated in this method. This method is modified by the enhancer

javax.jdo.spi.JDOImplHelper

instead. If the class has been enhanced for datastore identity, or if the class is abstract, null

JDOImplHelper.newObjectIdInstance(pcClass) - JDO Method

identity; newObjectIdInstance(Class, Object) should be used instead. If the class has been enhanced

PersistenceCapable.jdoNewObjectIdInstance() - JDO Method

identity. It is intended only for application identity. If the class has been enhanced

javax.jdo.spi.StateInterrogation

JDO Interface StateInterrogation This interface is implemented by a non-binary-compatible JDO implementation to provide state interrogation for non- enhanced persistent classes. A call to JDOHelper to get the status of an instance is handled internally if the parameter instance implements