Bug
Autocommit off: scheduling fails with new topics
Issue description
When a POST service creates a new topic and uses it as an argument for a scheduled service call, the job fails since the parameter was stored with the negative temporary topic id before the topic received its permanent system id.
Developer comments
Also sending an email fails.
Service calls with uncommited tobjects do not make much sense. If the functionality is really necesasry within the process put it into a domain class. But the temporary topic currently only exists within the PHP process and noone outside should know about it before the commit. While it could make sense and even be possible to implement the resolution of the service paramter since the tobject does exist in the current process and a POST and GET call remain in the process, only schedule leaves the process, this is a lot of work for little gain.
This means that the developer either has to explictly commit or the schedules are buffered and performed after the commit.
No explicit commits, thus buffered.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.