Bug #12190: Aggregate root detection does not work for non-standard repositories - TYPO3.Flow - TYPO3 Forge

TYPO3 Flow Base Distribution TYPO3.Eel TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Welcome Packages Applications

Bug #12190

Aggregate root detection does not work for non-standard repositories

Added by Karsten Dambekalns over 4 years ago. Updated about 4 years ago.

Status:

Resolved

Start date:

2011-01-13

Priority:

Must have

Due date:

Assigned To:

Karsten Dambekalns

% Done:

100%

Category:

Persistence

Target version:

TYPO3 Flow Base Distribution - 1.0 beta 1

Estimated time:

2.00 hours

PHP Version:

Complexity:

Has patch:

Affected Flow version:

Description

If a repository and the model it holds don't match via the naming conventions, the ReflectionService does not detect that the model is an aggregate root.

Associated revisions

Revision ebcddb26
Added by Karsten Dambekalns about 4 years ago

[!!!][BUGFIX] Resolve non-standard model/repository bindings

If a repository and the model it holds don't match via the naming
conventions, the ReflectionService did not detect that the model is
an aggregate root.

This involves a breaking change for those that are using the property
$objectType in their repositories. That needs to be changed to a
constant named ENTITY_CLASSNAME:
protected $objectType = 'FooBar';
needs to become
const ENTITY_CLASSNAME = 'FooBar';

As a bonus this change adds a new method getEntityClassName() to the
base repositories which can be used to find out which entity is managed
by a repository instance.

Change-Id: I7920587c4060f6583276b05e8686a997e113b7b7
Fixes: #12190