BT

InfoQ Homepage Presentations Rod Johnson: Are we there yet?

Rod Johnson: Are we there yet?

Bookmarks

Bio

Rod is the father of Spring. The Spring Framework open source project began in February 2003, based on the Interface21 framework published with Rod's best-selling Expert One-on-One J2EE Design and Development. Rod is one of the world's leading authorities on Java and J2EE development.

About the conference

JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.

Recorded at:

May 31, 2007

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Circular dependencies?

    by Oliver Gierke /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Nice one again, injecting domain model classes leads to circular dependencies between service layer and domain layer in my opinion. Consider following packages

    foo.bar.pethealth.domain
    foo.bar.pethealth.service
    foo.bar.pethealth.service.impl

    domain contains all domain classes as Vet, Pet a.s.o., service contains interfaces exposed to clients and service.impl contains the actual implementations. So I am forced not to have a domain object in the IdentityTagRegistrationService interface to not create a circular dependency.

    Okay, this question lead to the question if its reasonable to expose domain objects to service clients, but for some applications it would be overhead to create DTOs for that purpose 'cause you simply would copy most properties and getters and setters from the domain object to the DTO class and thus duplicate code and create (unnecessary) complexity. All the DTO would be quite anemic, too.

    Perhaps in the next lower layer the problem becomes more obvious. What if I need to save objects in the logic, or retrieve further objects? DAO interfaces obviously have to expose domain objects. If I had a dependency to the DAO in the domain object then, the circle s perfect.

    Any thoughts on that?

    Regards
    Ollie

  • Re: Circular dependencies?

    by Sato Tadayoshi /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Oliver,


    domain contains all domain classes as Vet, Pet a.s.o., service contains interfaces exposed to clients and service.impl contains the actual implementations. So I am forced not to have a domain object in the IdentityTagRegistrationService interface to not create a circular dependency.

    If we recognize IdentityTagRegistrationService as a "Service" in the DDD sense, it is also a domain element so no circular dependency occurs. (Quite confusing, but Service in DDD is not the same as services of Martin Fowler's Service Layer.) Anyway, I agree that IdentityTagRegistrationService is not a good name for explaining architecture of the sample app.


    Perhaps in the next lower layer the problem becomes more obvious. What if I need to save objects in the logic, or retrieve further objects? DAO interfaces obviously have to expose domain objects. If I had a dependency to the DAO in the domain object then, the circle s perfect.

    Again, if you include DAO interfaces into domain packages and separate them from DAO implementations in dao package, circular dependencies disappear. This technique is Separated Interface pattern. In this case, DAO interfaces can be regarded as "Repository" of DDD and repositories are residents of domain model in their own rights.

    SATO, Tadayosi
    www.ouobpo.org

  • Great stuff. Let's go further.

    by Eelco Hillenius /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    That was a good presentation, and indeed how much better does the Java landscape look today. I do hope that Rod and friends someday will take up the defense for OOP in web applications (additionaly with AOP if you want). Clear responsibilies. Encapsulation. All that good stuff should have a place in the web tier like it has in the rest of your software.

  • Good summary

    by Rickard Öberg /

    Your message is awaiting moderation. Thank you for participating in the discussion.

    This was an excellent presentation, that I hope many many people will watch. I wholeheartedly agree with the background description and problem summary, and with the ideas of moving more towards an object-oriented domain model. We have been using this approach in SiteVision for a long time, with AOP as the enabling technology, and have found it to be a good way to avoid the pitfalls Rod outlines.

    That being said, I think there are better ways to solve this than to use AOP. But, one step at a time. First everyone must understand the absolutely horriffic situation we are in today, as described in the presentation.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.