Page 4 of 4 FirstFirst ... 234
Results 31 to 31 of 31

Thread: Spring Roo with a services/DAO architecture

  1. #31
    Join Date
    Jul 2008
    Posts
    239

    Default

    All I am saying is that records should not be 'active'.

    It is BOILER PLATE.


    Code:
    account.calculateYearEndResults()
    should be (in ServiceManager class)

    Code:
    public Result calculateYearEndResults(Account a)

    In short: records should be minimal javabeans. only getters and setters.


    in other words:

    what OOP should have done, here its done by a tool which is bad (which doesnt mean that the tool does only what OOP can do).



    However, transactions at the entity layer will, by default, participate in a transaction declared in a service.

    there is no entity layer.

    entities MUST NOT have a field of type EntityManager !
    that is a sufficient condition for all problems to go away.
    Last edited by sandstorm; Dec 5th, 2010 at 11:22 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •