>
> There seem to be three options suggested by existing Turbine code.
>
> 1. Use the Peer approach used within org.apache.turbine.om.*
> This uses village.
> 2. Use the OPaL, which seems to be much more sophisticated
> but which I understand is incomplete. OPaL does not use
> village.
> 3. Use village and JDBC without having a Peer for each
> major object. This seems to be the approach taken by Jyve.
>
I would add yet another option:
4. Use Castor (http://castor.exolab.org)
--Alejandro
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
- Re: What persistence framework recommended f... John McNally
- Re: What persistence framework recommend... Scott Tavares
- Re: What persistence framework recommended f... Scott Tavares
- Re: What persistence framework recommended for Turbin... Dave Bryson
- Re: What persistence framework recommended for Turbin... jon
- Re: What persistence framework recommended for T... Stephen Adkins
- Re: What persistence framework recommended f... John McNally
- Re: What persistence framework recommend... Dave Bryson
- Re: What persistence framework recom... John McNally
- Re: What persistence framework recommended for T... Scott Tavares
- Re: What persistence framework recommended for Turbin... Alejandro P. Revilla
