Why Jongo 1.0 removed support for private properties

Question

Recently I migrated from Jongo 0.4 to Jongo 1.0, and suddenly I started to receive this exception:

! java.lang.IllegalArgumentException: Unable to set objectid on class: class *Myclass*
! at org.jongo.ReflectiveObjectIdUpdater.updateField(ReflectiveObjectIdUpdater.java:72) ~[jongo-1.0.jar:na]
! at org.jongo.ReflectiveObjectIdUpdater.setObjectId(ReflectiveObjectIdUpdater.java:60) ~[jongo-1.0.jar:na]
! at org.jongo.Insert.preparePojo(Insert.java:71) ~[jongo-1.0.jar:na]
! at org.jongo.Insert.insert(Insert.java:56) ~[jongo-1.0.jar:na]
! at org.jongo.MongoCollection.insert(MongoCollection.java:140) ~[jongo-1.0.jar:na]
! at org.jongo.MongoCollection.insert(MongoCollection.java:132) ~[jongo-1.0.jar:na]
...

That means that Jongo now has problems setting a private field, which in 0.4 wasn't a problem.

Is there some reason for this limitation?

No, actually I reverted to 0.4, as I was satisfied with it. I was only curious why would they remove such handy functionality. — Juraj, Jul 25 '14 at 09:49
My guess: that's more likely a regression. That's why I suggest you to try 1.1, it should have fixed this ;-) — yves amsellem, Jul 25 '14 at 11:19

score 0 · Accepted Answer · answered Jul 27 '14 at 20:04

0

Jongo stills 'support' private properties in v1.0

Nevertheless due to a regression it was unable to handle private id field.

This has been fixed in v1.1 : https://github.com/bguerout/jongo/issues/198

If you have a Maven pom.xml, just update it with :

<dependencies>
  <dependency>
   <groupId>org.jongo</groupId>
   <artifactId>jongo</artifactId>
   <version>1.1</version>
  </dependency>
 ...
</dependencies>

answered Jul 27 '14 at 20:04

Benoît Guérout

1,977
3
21
30

Thanks you both Benoit and Yves, in version 1.1 there is really no problem. – Juraj Jul 28 '14 at 08:25

Why Jongo 1.0 removed support for private properties

1 Answers1