Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
In-Reply-To: 
 <OFB10D5998.CC77006F-ONC12576E0.00290BEF-C12576E0.002E6A89@seitenbau.net>
References: 
 <OFD9F4FB90.5B09139F-ONC12576DC.00350202-C12576DC.0035F245@seitenbau.net>
 <012101cabd36$818c2710$84a47530$@com>
 <OFB10D5998.CC77006F-ONC12576E0.00290BEF-C12576E0.002E6A89@seitenbau.net>
Subject: RE: torque 4 plan (was: RE: Release candidate of torque 4 site -
 please
 review)
To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Message-ID: 
 <OFA922AFB1.064EE539-ONC12576E0.003068D7-C12576E0.00307E2D@seitenbau.net>
From: Thomas Fischer <fischer@seitenbau.net>
Date: Mon, 8 Mar 2010 09:49:39 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII

> > What I also would like is some kind of plan on what Torque4 actually
will
> > contain. It would be nice to know what the "heavy development"
mentioned
> on
> > the first page is and what is left of it.
>
> There were occasional discussions about this during the last three years,
> and most certainly I do not remember everything. And also, this is my
> personal list, so everything I say here is subject to community approval:
>
> What will most certainly change:
> - package and class names in the generator (the "generator" name is too
> overloaded, so the name of the generator class will change and the "gf"
> package name will change to "generator")
> - configuration syntax in the generator will reflect the class name
changes
> in the generator
> - the templates need to be adapted to the generator configuration changes
> - ant support for the generator will be added
> - something needs to be done about the ant tasks that were in 3.3. but
are
> not yet present in 4.0.
> - external schema support will be added in the templates
> - package structure of the templates (the id table sql templates are
> currently not in the sql package which is confusing)
>
> What will probably change:
> - the Criteria class might get refactored (no inheritance of HashMap etc)
> or might get an alternative
> - There might be a custom type for column Ids (not the String constants
> used now)
> - There might be an alternative to static peer classes to ease plugging
in
> of an alternative implementation
>
> What will hopefully not change
> - migration from Torque3 to Torque4 should be as painless as possible. So
> the behaviour of the runtime should change as little as possible.

ouch, forgot one and another:

what will most probably change:
- village will be removed from the runtime (and as a result from the
templates)

what might change:
- subject to further discussion, java 1.4 might not be supported any more
in the runtime.


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org