Bug #3477

Objects added to a (persistence) repository don't have have a uuid

Added by Robert Lemke about 6 years ago. Updated almost 5 years ago.

Status:Resolved Start date:2009-05-27
Priority:Must have Due date:
Assigned To:Karsten Dambekalns % Done:

100%
Category:Persistence
Target version:TYPO3 Flow Base Distribution - 1.0 alpha 1
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

Newly created objects which are added to a repository don't have a uuid before they are persisted:

    /**
     * @param \F3\Releazr\Domain\Model\Release $newRelease
     * @return string
     */
    public function createAction(\F3\Releazr\Domain\Model\Release $newRelease) {
        $this->releaseRepository->add($newRelease);
        $this->redirect('show', NULL, NULL, array('release' => $newRelease));
    }

The redirect in the above example doesn't work because the URI needs to know the UUID of $newRelease which yet doesn't exist.

Solution: Let the (release) repository create a UUID and let the CR take that UUID as a hint for later persistence.

Associated revisions

Revision 734da3c3
Added by Karsten Dambekalns about 6 years ago

FLOW3:
  • entities now get an UUID set through AOP upon creation which is used later on, resolves #3477
TYPO3CR:
  • getUUIDByObject now looks for UUID set by FLOW3 through AOP, refs #3477

History

#1 Updated by Karsten Dambekalns about 6 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r2442.

Also available in: Atom PDF