*persistence transparency* <=> *waste of efficiency*
There are no good systems that solve that yet. It only works for very
simple schemas.
Besides,
(1) Not using that kind of layer does NOT mean that you have to
concatenate Strings;
(2) The use of Javabeans is abused.
For (1) I use SQL generators for the most common operations and SQL
templates - defined in an XML file - for the others. Having SQL defined
outside the Java code often saves a lot of time and avoids the
concatenation mess.
For (2)... just go to the jakarta-commons mail archives and check the
discussions about the DynaBeans stuff.
Have fun,
Paulo Gaspar
> -----Original Message-----
> From: Andrus Adamchik [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 31, 2002 8:43 PM
> To: [EMAIL PROTECTED]
> Subject: RE: J2EE considered harmful
>
> ...
>
> Well, if EJB (or others) are doing it wrong, it doesn't mean that Object
> Relational approach is bad. I agree that objects mapped straight to the
> rows one to one are not of much use by themselves. But they provide
> something that you will need to build your less fine grained objects,
> namely *persistence transparency*. By the same token you can say that any
> objects that use Java Bean pattern are useless, since all they
> have is get
> and set methods.
>
> But well, some people may like to concatenate SQL strings every time they
> want to get some data written or read to/from the database. The keyword
> here is "productivity".
>
>
> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> - Andrei (a.k.a. Andrus) Adamchik
> http://objectstyle.org
> list email: andrus-jk at objectstyle dot org
> personal email: andrus at objectstyle dot org
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
