Originally posted by Ajith Kallambella:
Not exactly an answer to your question, but I think you are clearly going down the slope of "everything is an EJB". Does flight and Seat have to be an EJB?
Hi Ajith,
I see your point that "not everything qualifies for an EJB".
But I think Flight is definitely a "Business Object". Whether it gets implemented as a remote entity bean, local entity bean or a simple bean could be debatable.
For example: if down the road, the system requires some maintenance modules for maintaining/publishing flight information then planning a "Business Object" called Flight or FlightDescription helps.
In Petstore, the famous "Customer" diagram depicts 5-6 different objects. Sun implemented all of them as Local Entity beans. May be just 2 or 3 objects would have met the requirement.
regards,
Deepak