Bug #1724
Unserialzing of persisted objects will call the __wakeup function
| Status: | Resolved | Start date: | 2008-10-15 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
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.
Associated revisions
FLOW3:
- __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
History
#1 Updated by Karsten Dambekalns over 6 years ago
- Status changed from New to Accepted
- Assigned To set to Karsten Dambekalns
#2 Updated by Karsten Dambekalns over 6 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1912.