MVC should know about entities lying in the session
If you want to prepare/edit/create an entity over some steps before you want persist it in the database, you will put it somewhere in the session. So far so good. As soon as you have an entity lying in the session and want to forward or redirect it to another action the persistence manager will be asked to return the identifier, to encode and decode the object to/from its identity array. As the entity is not yet added to a repository, the persistence manager will return FALSE and the forward/redirect breakes.
We should enable the persistence manager to know about every entity in the session and look at them before asking the underlying persistence layer (e.g. doctrine).
Updated by Karsten Dambekalns over 10 years ago
- Subject changed from Persistence manager should know about entities lying in the session to MVC should know about entities lying in the session
- Category changed from Persistence to MVC
- Status changed from New to Resolved
- % Done changed from 0 to 100
This should be done elsewhere, not in the persistence manager. If an entity is not yet persisted, why on earth should the persistence manager know about it?
Updated by Andreas Förthner about 9 years ago
- Status changed from Resolved to New
- Assignee deleted (
Sorry, I don't see the whole issue solved. The basis is now there but there a still one thing missing:
All entities lying in the session have to be registered as new objects on session initialization in the respective __wakeup methods.