File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes EJB and other Java EE Technologies and the fly likes Business Object Patter Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Business Object Patter" Watch "Business Object Patter" New topic

Business Object Patter

laxmikant shimpi

Joined: Sep 18, 2001
Posts: 21
I have confusion about the business object design pattern.
First of all, I have checked on sun site. There is no design patten or strategy which mentions the Business Object Design Pattern.
What according to my knowledge is IBusinessObject, BusinessObjectImpl and BusinessObjectManager is required which actually form this pattern.
We are not using entity beans instead using DAOs to access the database and using BOManager only for retrieving/finding the value objects and construct business object out of it.
Can we not use directly session fa´┐Żade to carry out the functionality of BOManager
Can someone clear my confusion? If possible, please give me links.
Thanks and Regards,

Sun Certified Java Programmer
Ajith Kallambella

Joined: Mar 17, 2000
Posts: 5782
In the context of "Business Object", think of entity beans and/or DAOs are the gateways to persistence storage. The idea is to present the client with an object a.k.a a bag of data and still maintain the flexibility to change the underlying implementation. Although creating composite(coarse-grained) entity beans is a step in the right direction, I think the Business Object pattern is all about abstraction of data representation. It is not about how the data is populated or who populates it( the J2EE pattern description tends to hint in the wrong direction), but it is about the "client view" of the data. A sort of composite transfer object if you will.
In the past I have implemented my coarse-grained transfer objects as busines objects. They implement an interface and the clients know only about the interface, but not about the implementation. This allows you to implement different flavors of the business object eg., data carried in a hashmap, data carried around as one big concatenated string (although not recommended) and so on, while still conforming to the declared interface.

Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
Seetesh Hindlekar
Ranch Hand

Joined: Feb 13, 2004
Posts: 244
Hey Laxmikant.
Enjoying and manipulating Business patterns eh.
BTW, where r u implementing Session Facade in lieu of Business Delegate?
Does ur code relate to petstore example or something else?
EPFGL still bugging u?
I agree. Here's the link:
subject: Business Object Patter
It's not a secret anymore!