[TYPO3-50-general] Last minute concept fix? Incosistent class naming for domain models ...

[Martin Kutschker]

Daniel P?ötzinger schrieb:

> 
> That might look good on the first place - but normally thats not how you
> want to group your Domain Model.
> If the application grows you rather want to group them in packages (with
> high coupling - low cohesion) like:
> 
> Domain/Model/
>   Customer/
>   Products/
>   Contract/
>   Order/
>     Payment/
>   ...

Wouldn't that be like this?

Domain/
 Customer/
   Customer.php (or CustomerModel.php)
   CustomerService.php
   CustomerRepository.php

When you group the files per "package" (or "module") than it makes IMHO
little sense to have "Model" in the directory name.

Masi