None of these solutions involve writing sql (unless you want to) or jdbc
code.

If you decide against cmp2, I'd try jdo next. I think it is the most
likely to survive and allow you to trade implementations. Both ojb and
the jboss persistence engine will eventually have jdo available. (ojb does
now to some extent, but I don't know to what extent. It relies on the jdo
RI for most of the work).

david jencks

On 2003.04.16 16:14 Phil Shrimpton wrote:
> On Wednesday 16 April 2003 17:27, David Jencks wrote:
>
> Hi,
>
> > TJDO (sourceforge) is an open source jdo implementation
> >
> > OJB (now on apache) is an open source odbmg3 implementation
> >
> > I think Hibernate has recently added firebird support. I
>
> Thanks David, there are a few there that need furthur investigation.
>
> > Are these approaches really simpler than jboss + cmp2 + xdoclet?
>
> Possibly not. I was hoping there was something 'in the middle' of 'plain
>
> JDBC' and full blown cmp2 that has passed me by.
>
> > I think
> > you get much better caching and configuration flexibility with cmp2.
>
> Whilst cmp2 does seem to be overkill for what we need, it does have the
> benefit that we do have experience with it, unlike the other frameworks.
> If
> we were just using Firebird, we would have probably gone with 'just' JDBC
> and
> SQL, but adding a second database engine into the mix, and things grow
> (two
> lots of metadata to develop maintain, two sets of SQL statements etc.)
>
> Phil
>
> --
> Linux 2.4.4-4GB
> 8:04pm up 11:56, 1 user, load average: 0.40, 0.10, 0.03
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>