This message was deleted.

This message was deleted.

I am encountering a problem using Domain classes containing properties that are mapped as GORM/Hibernate User Types in conjunction with application level caching of those entities using EH Cache. A NotSerializableException is raised identifying the User Type class as not serializable when EH cache attempts to serialize the enclosing Domain object. That is, it seems to be taking the property type from the GORM mapping rather than following the Groovy type of the property. This doesn’t seem right - GORM/Hibernate serialization to/from database columns should be orthogonal to Java/Groovy serialization for caching should it not?

I am working with a codebase that has evolved over many years. Some of its older tests make use of a ‘build’ static method on Gorm Domain classes to construct them. Can anyone point me to where I can find documentation on how it behaves, particularly wrt any auto-assignment of property values and execution of validation against constraints…?

I am using the gorm/ Hibernate feature to map a columns to a custom type. In my custom UserType implementation the method to handle the column value (nullSafeGet) accesses a Grails DataService. However this is proving to be problematic in that after the successful call to this Data service the handling of other columns is failing with a JDBC/Postgresql error that the ResultSet is closed. My suspicion is that the call to this other Data service is causing this side effect and that I should avoid any other database calls in this call-back. However before I look into changing the design I thought it worth reaching out here to see if anyone can confirm my hypothesis and suggest any other workarounds other than avoiding further database access…?

@Kojus has left the channel