JDBCStore Objects No Longer Have Mementifier When Retrieved from Cache
Description
I suspect this is a bug in how objects are serialized/deserialized when persisting in the JDBC store. Hopefully, it's not terribly difficult to fix. Steps to replicate the issue:
Server config: ACF 2018+ DB: SQL Server (make sure Enable long text retrieval (CLOB) is enabled in cf admin!) Note: Did not test with MySQL.
1. Create a new Coldbox app 2. Install Mementifier 3. Create a simple model (e.g. `user`) with a few properties like this:
4. Configure the cache to use the JDBC Store like this (make sure your DSN exists):
5. Create a handler that will instantiate the object, set it to cache, retrieve it, and attempt to run getMemento()
You will see an error that looks like this: "General application error: Neither the method getMemento was found in component D:[your path]\user.cfc nor was there any default method with this name present in any of the implementing interface.", "Detail: Ensure that the method is defined, and that it is spelled correctly.",
Activity
Show:
David LevinJanuary 20, 2022 at 5:57 PM
Edited
Thank you! Yeah, I suspected it had something to do with mixins. I agree with you and think it is a good policy to cache raw data instead of objects with behavior. It’s probably more efficient as well. I just created another (maybe related?) issue with Lucee as well. It may fall under the same category.
Luis MajanoJanuary 20, 2022 at 5:48 PM
Hi welcome to the wonderful world of pain using serialization/deserialization. This is a know behavior of any object that has dynamic methods injected in them. ColdFusion will serialize the object to it’s best ability. However, injected references and mixins are not part of the serialization blueprint and thus are not deserialized once the object is inflated back.
Meaning, you can serialize the user object, but there is never a guarantee any dependencies or mixins will be reinstated once it’s inflate back to its state. What I would recommend is to never rely on CF serializing objects for you when using distributed caches like jdbc, redis, mongo, etc.
There is too much it assumes and you have no control over it. So either, you build Java objects that can serialize deserialize accordingly, or stick to native data structures. You are already using mementifier, and it was built not only for APis but also for setting and saving state. Thus following the memento pattern.
Get the memento, store it in the cache. And when you need it, get it and set it back INTO the object.
Known Error
Pinned fields
Click on the next to a field label to start pinning.
I suspect this is a bug in how objects are serialized/deserialized when persisting in the JDBC store. Hopefully, it's not terribly difficult to fix. Steps to replicate the issue:
Server config:
ACF 2018+
DB: SQL Server (make sure Enable long text retrieval (CLOB) is enabled in cf admin!)
Note: Did not test with MySQL.
1. Create a new Coldbox app
2. Install Mementifier
3. Create a simple model (e.g. `user`) with a few properties like this:
4. Configure the cache to use the JDBC Store like this (make sure your DSN exists):
5. Create a handler that will instantiate the object, set it to cache, retrieve it, and attempt to run getMemento()
You will see an error that looks like this:
"General application error: Neither the method getMemento was found in component D:[your path]\user.cfc nor was there any default method with this name present in any of the implementing interface.",
"Detail: Ensure that the method is defined, and that it is spelled correctly.",