On 11/15/01 3:01 PM, "Peter Royal" <[EMAIL PROTECTED]> wrote:
> On Thursday 15 November 2001 02:57 pm, you wrote: >> The Torque code has been decoupled from Turbine and Martin Poeschl and >> myself are currently writing a testbed to find the problems that are still >> present in the code. I'm working on making the connection pool pluggable >> and we are moving toward using the design of Scott Ambler to make Torque a >> general persistence layer. >> >> What little documentation there is can be found here: >> >> http://jakarta.apache.org/turbine/torque > > damn. i wish i had found this before i wrote my own :) Your tool might work better for your situation. Torque at the moment is very datamodel-centric and is really useful for those who are used to working from the datamodel but not ideal for people (like myself) who are accustomed to working with an object model first. Torque creates an object model which is really a thin veneer over top of a datamodel. So what we provide now is a table mapping to a single object, this is rarely complete enough a solution in the real world but is fine if you have complete control over a project. I am trying to work in the designs of Scott Ambler to make Torque a general persistence layer for an object model. For example an application may consist of attributes retrieved from any number of different tables (possibly in different databases), an XML source or any other location. Scott Ambler's design allows for this, as well as decoupling the datamodel completely from the object model so that changes in the way your data is stored does not affect application programmers. Torque is not there yet but I'm hoping development will move along briskly once the testbed is complete. > -pete -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
