It seems that I have found a bug in HibernateBeanManager::holdPersistentObject()
#811 // Get property value
#812. Method readMethod = descriptor.getReadMethod();
#813. readMethod.setAccessible(true);
(Of course, I wish I simply do something wrong :)
When I transfer an object from server to browser, which is not persistent object and has nothing to do with Hibernate, Hibernate4Gwt checks it anyway and performs above code. However, this transferred object doesn't have "readMethod" for one of it's property! It has IndexedReadMethod instead! And the above code fails with NullPointerException.
I think that a case with indexed method should be treated somehow.. Or maybe I do something wrong and my non-hibernate classes are checked by mistake?
Thanks for your attention!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you try the latest version from SVN (branch 1.1). I made some improvements on holdPersistentObject method, and the bug you mention could have been fixed...
Regards
Bruno
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
holdPersistentObject is known to have some issues in release 1.1.1
I fixed them in Subversion, and they will be included in release 1.1.2, but they are currently only available on SVN branch '1.1'.
Can you checkout latest version of source, build hibernate4gwt, test with this new version and tell me if the issue you mentioned is solved (I think it should be the case) ?
Regards
Bruno
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello!
It seems that I have found a bug in HibernateBeanManager::holdPersistentObject()
#811 // Get property value
#812. Method readMethod = descriptor.getReadMethod();
#813. readMethod.setAccessible(true);
(Of course, I wish I simply do something wrong :)
When I transfer an object from server to browser, which is not persistent object and has nothing to do with Hibernate, Hibernate4Gwt checks it anyway and performs above code. However, this transferred object doesn't have "readMethod" for one of it's property! It has IndexedReadMethod instead! And the above code fails with NullPointerException.
I think that a case with indexed method should be treated somehow.. Or maybe I do something wrong and my non-hibernate classes are checked by mistake?
Thanks for your attention!
Hi Alex,
Did you try the latest version from SVN (branch 1.1). I made some improvements on holdPersistentObject method, and the bug you mention could have been fixed...
Regards
Bruno
Unfortunately, I use exactly 1.1.1 version..
Hi Alex,
holdPersistentObject is known to have some issues in release 1.1.1
I fixed them in Subversion, and they will be included in release 1.1.2, but they are currently only available on SVN branch '1.1'.
Can you checkout latest version of source, build hibernate4gwt, test with this new version and tell me if the issue you mentioned is solved (I think it should be the case) ?
Regards
Bruno