Fast Object Database for Java - with JPA/JDO support

Issue #153: Object DB Explorer fails to open database

Type: Bug reoprtVersion: 2.0.5Priority: NormalStatus: FixedReplies: 5
#1

Hello,

I am trying to integrate Object DB into my tapestry project which will use spring-security. I have created an entity class named "Role" which implements springs "GrantedAuthority" interface. The code runs fine. i.e. Role objects are getting persisted in the database. But when I try to open the database using Object DB Explorer, it fails. 

I have attached all the related files. 

Regards,

Md. Towfique Imam.

application/vnd.oasis.opendocument.database icon guest.odb (256 KB)
Object DB Explorer fails to open this database
application/octet-stream icon objectdb-explorer.err (1.17 KB)
Object DB Explorer error log file
text/x-java icon Role.java (1.41 KB)
Entity class definition that is reported on error log file.
#2

There was a bug in build 2.05_03 that was fixed in build 2.05_04.

I just opened your sample odb file using the Explorer of 2.1.0 with no problems.

Please upgrade to ObjectDB 2.1.0.

 

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#3

Thanks. The solution worked. 

#4

Hello again,

I have another case where Object DB Explorer fails to open database. 

I have a BaseEntity class which has an EntityListener named AuditListener associated with it. Again the code runs fine but Object DB Explorer fails to open the database. 

All the related files are attached.

Regards,

Md. Towfique Imam.

 

text/x-java icon BaseEntity.java (0.877 KB)
BaseEntity Class
text/x-java icon AuditListener.java (0.313 KB)
AuditListener Class
application/vnd.oasis.opendocument.database icon guest_0.odb (256 KB)
Database file
application/octet-stream icon objectdb-explorer_0.err (2.86 KB)
Object DB Explorer error log file
#5

Thank you for this report.

There was a problem in handling listeners and callback methods.

Version 2.1.1 fixes this issue.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#6

Thanks for the quick fix. Version 2.1.1 fixed the issue. 

Post Reply