This week's book giveaway is in the Big Data forum.
We're giving away four copies of Elasticsearch in Action and have Radu Gheorghe & Matthew Lee Hinman on-line!
See this thread for details.
The moose likes OO, Patterns, UML and Refactoring and the fly likes Session to persistence layer design Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Elasticsearch in Action this week in the Big Data forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Session to persistence layer design" Watch "Session to persistence layer design" New topic

Session to persistence layer design

Pho Tek
Ranch Hand

Joined: Nov 05, 2000
Posts: 776

I've just inherited a web application that uses the above architecture.
I can't fathom why there needs to a BMP entity layer over the DAO. The
reason I got from one of the developers is that BMP beans makes the DAO
"remoteable". I'm not sure if that's such an advantage anyway - who would
want to distribute their Service Layer from their persistence layer ?
So my question to you is this, if you were asked to throw away the BMP entity layer, what new layer(s)/abstraction(s) would you replace it with ?


Lasse Koskela

Joined: Jan 23, 2002
Posts: 11962
With nothing, I think.

Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Kyle Brown
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
I'm with Lasse. Trash the BMP's. They're a curse.

Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at for other WebSphere information.
I agree. Here's the link:
subject: Session to persistence layer design