Unserialzing of persisted objects will call the __wakeup function
|Priority:||Must have||Due date:|
|Assignee:||Karsten Dambekalns||% Done:||
|Has patch:||FLOW3 version affected:|
If a user for some reason wants to serializa an object that has been persisted, it will call the persistence frameworks __wakeup function upon unserializing, which will expect stuff to be available in $GLOBALS and then fail.
I didn't test it, just came across looking into the persistence code.
- __wakeup() is no longer handled in a special way in AOP to support persistence, fixes #1724
- changed the persistence aspect to no longer attach to __wakeup(), refs #1724
- replaced reconstituteObject() by three seperate methods to allow two-step reconstitution, refs #1849
- split initialize() into seperate methods in FLOW3 persistence backend
- the FLOW3 persistence DataMapper now uses two-step reconstitution allowing to load bidirectional object relations
- the FLOW3 persistence DataMapper asks the object Builder to inject setter dependencies during reconstitution, fixes #1849
Updated by Karsten Dambekalns over 4 years ago
- Status changed from New to Accepted
- Assignee set to Karsten Dambekalns