Home » Search

About version

131-140 of 200 Refresh
Forum
2

JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception

-plugin     < version>2.1.1 version>             version of JBoss was 7.0.x at that time and lots of declaration ... .Final/modules/com/objectdb/main - module.xml - objectdb-jee-2.4.0_04.jar   module.xml: version
Forum
2

ArrayIndexOutOfBoundsException

Hi, I've been getting the following exception when trying to query ObjectDB in server mode version ... to the stack trace it is related to failed schema evolution. The number 36 indicates type version number 36 (i.e. after 35 modification of some entity type). You have an object with that type version
Forum
2

Request clarification of changes to accessor enhancement policy (non-getter prefix instead of getter suffix) AND annotations

enhanced additional getters/setters, because the additional methods now use (since about version 2-6-5 ... the method as a setter or getter), prior to version 2-6-5: [accessor_name]_odbHidden ... .objectdb.com/object/db/database/ version/2-6-5     - Renamed internal Enhancer hidden methods to non
Issue
2

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

it will report: Java/JVM version: 1.8 Java/JVM detail version: 1.8.0_74 ObjectDB enhancer: begin ... .jar Under /lib there are 2 versions: lib/objectdb-2.6.3_04.jar* lib/objectdb-2.6.9.jar In top-level build.xml change this property to use that version during enhancement (use File view mode not
Forum
2

Problem using Maven Repository - Enitiy Class will be ignored

>com.objectdb objectdb < version>2.6.2 version> I got follow Java Warning that tells me that Entity Class will be ignored ... > com.objectdb < version>2.6.2 version>
Forum
2

Remove an entity which attributes were changed - OptimisticLockException

with the last ObjectDB version. ObjectDB maintains a version number for every entity object, which is increased on every update. An OptimisticLockException is thrown when that version number indicates ... this is not the case. In order to understand the cause, please track the object version
Issue
1

ObjectDB BIRT Driver Update

. In the current implementation ObjectDB is embedded in the driver. Any 2.x version of the driver ... is fixed for all 2.x versions. However, since the client-server protocol is occasionally being updated, there should be a match between the ObjectDB BIRT client-server protocol version and an ObjectDB
JDO Doc
1

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameter)

Method javax.jdo.Query void addSubquery(   Query sub,   String variableDeclaration,   String candidateCollectionExpression,   String parameter ) Add a subquery to this query. The String version of the method binds the named expression to the parameter implictly or explicitly declared in
JDO Doc
1

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters)

Method javax.jdo.Query void addSubquery(   Query sub,   String variableDeclaration,   String candidateCollectionExpression,   Map parameters ) Add a subquery to this query. The Map version of the method treats the key of each map entry as the name of the parameter in the subquery, with or
JDO Doc
1

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters)

is the extent of the candidate class. The String... version of the method binds the named expressions in turn