commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Juozas Baliuka" <>
Subject Re: [Simper] Re: Bean storage in database
Date Mon, 04 Feb 2002 16:04:31 GMT
It is very intersting for me, can I help ?
----- Original Message -----
From: "Bryan Field-Elliot" <>
To: "Jakarta Commons Developers List" <>
Sent: Monday, February 04, 2002 3:18 PM
Subject: Re: [Simper] Re: Bean storage in database

> On Sun, 2002-02-03 at 11:34, James Strachan wrote:
>     Cool. BTW I could maybe help with the Digester & XML stuff if you
> That would be great. Should be in the few days that I get a site up to
> support it (with CVS etc). As you might imagine, I have a "real job"
> which obviously takes precedence.
>     One other thing to keep in the back of your mind when you're
>     refactoring things. Once its in CVS somewhere - hopefully the sandbox
>     failing that sourceforge - I'd be quite interested in adding support
>     'real' beans.
>     I think DynaBeans are perfect for queries and for when the Java object
>     is dictated by the database schema. Its also very common to need to
write a
>     web app for an existing database, where hand coding beans to represent
>     database is a wasted effort. Though it would be nice to support the
>     way around as well, that Java business objects are written first and
>     gets used to persist them and that the database schema comes
>     The Simper code is mostly based on DynaBeans and its pretty easy to
wrap a
>     DynaBean around a real bean so I'm hoping that mostly Simper won't
>     know if real or dyna beans are being used. To get the 'mark as dirty'
>     features in your SimperBean we could use BCEL or JDK1.3's dynamic
>     to generate wrappers that detect when bean setters are called. The
>     thing about this would be we could
>     use Simper to persist any Java Bean, as well as DynaBeans. There's an
>     object-relational can of worms that this could open but hopefully
we'll be
>     able to keep it simple.
> That does sound interesting -- wrapping existing beans (POJO's) into
> Simper. Hopefully it can be done in a clever, yet simple way, rather
> than bloating it up into a big O/R tool. That's the mantra I hope is
> always maintained -- keep it simple yet clever. I've never worked with
> dynamic proxies, that sounds interesting.
>     BTW I keep wanting to type Simpler rather than Simper. The project
>     didn't start out as a typeo did it ;-)
> The word Simper does bounce awkwardly around the brain doesn't it? But
> it's correct -- Simple Persistence - Simper.
> Bryan

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message