RE: Application Services and Framework Annotations

Dear Nikolaos,

You are right, please
pay attention t those projects you have already seen, they have had their
stress on demonstration of DDD concept. In fact the aim was not to make every
things in the project perfect.

If you want to do
Authorization or validation , as per as my knowledge you have to make another layer
such as Validation.Domain.Service (VDS) then process of validation must be done
through mentioned logic implemented in (VDS). So to achieve Logging/security/... issue and
other stuff you can follow same approach.

Ultimately whatever approach
you are going to take, that must not lead your Core (includes entities) depends
to others, that is strongly prohibited due to high coupling.

Greetings,

Babak Maser.

--- In [email protected], <[email protected]> wrote:

Hi everybody,

In many of the sample DDD applications that I reviewed, framework
specific annotations are used to annotate the Domain Model (e.g.
@Table, @Entity) and the Application Services (e.g. @Transactional,
@PreAuthorize).

I believe that the Application Services and especially the Domain
Model should not depend on the framework we are using.

Do you agree with the statement above?

For example, in the Domain Model we define Repository interfaces
that are implemented in an infrastructure layer. Thus, the Domain
Model is ignorant of the persistence mechanism.

Similarly, Application Services manage security and transactions but
depend on Security/Transaction interfaces defined in the Application
layer.

Greetings,

Nikolaos Papagrigoriou

- English
- detected

- English

- Greek

- German

- English

- Greek

- German

__._,_.___

Your email settings: Individual Email|Traditional

Change settings via the Web (Yahoo! ID required)

Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured

Visit Your Group |
Yahoo! Groups Terms of Use |
Unsubscribe

__,_._,___