On Sun, 20 Feb 2000 11:13:24 +0100, Robert =?iso-8859-1?Q?Kr�ger?=
<[EMAIL PROTECTED]> wrote:
>encapsulate the query and the result in an object oriented way and make it
>part of your facade. IMHO that's the most straight forward way to do it. I
>try to avoid having to write sql and jdbc code where I can but you have to
>be careful in deciding whether you're actually shooting yourself in the
>foot by trying to avoid them at any cost. I have been using entity beans
>(especially cmp) extensively in the past few months and I can now observe
>the tendency to go back to the basics where it makes sense. why just use a
>relational database as a dumb data bucket and not use its features?.
Because I want to think of my business objects in terms of the
real world, not as rows and columns. I want to work with domain objects
and not care if the entity beans are implemented using a rdbms, odbms or
whatever. Rapid design means abstracting away the tedious details (sql) and
working through the abstractions (datamodel).
Circumventing the datamodel feels like I am breaking encapsulation, and all
OO programmers are practically trained form birth to avoid that.
After all the hard work implementing the entity bean model it just feels
like a shame not to use it. Ok, no more whining now.. :) thanks for the advice,
lets see if anyone has any other ideas....
take care,
Floyd
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
