Hi Thoralf,
I have tested the patch, and removed a few bugs from the beans part, but
it looks good. I need to set the right configuration defaults and write up
some documentation, though.
Would you mind to sign a cla and fax it to the ASF office ? see
http://www.apache.org/licenses/#clas
Thanks a lot,
Thomas
On Fri, 23 Dec 2005, Thoralf Rickert wrote:
Okay, now I've 'cheated' the OM templates in Torque 3.2 to enable Java5 features. I've
tested the Peer and Object generation. Everything else is untested (Managers and Beans)
but implemented as good as possible. The templates are currently Java5 enabled. You have
to UNSET the "enableJava5Features" variable. This makes it possible to define a
configuration key and make the variable visible, when the configuration file this says.
So I didn't change the Torque Source code (that's maybe you task).
http://thoralf.log-out.net/tmp/java5enabled-templates.zip
Merry Christmas
Thoralf
-----Ursprüngliche Nachricht-----
Von: Thoralf Rickert
Gesendet: Freitag, 25. November 2005 12:07
An: 'Apache Torque Developers List'
Betreff: AW: Torque with Java5 features
Just to make sure that I understood you correctly: You
were able to
convert the templates without chamnging the Runtime jar, and it
worked ?
Jo.
- Testing would be more complicated. At the moment, it is
already a
nuisance to change the databases by hand, and to change
the idtable
property by hand. To not spend my life testing, I do
admit I usually
do not switch other parameters. So this would add another
parameter
to be
switched; this gets to a point where something atomatic would
have to be written.
Just thinking: What about a script that compiles and verifies
each possible configuration?
- We already have too many generator parameters. We need to think
about that problem. But I would guess in this case, a
configuration
parameter would be the only sensible way (maintaining two sets of
templates, with managers and withou them, is a nuisance
already, I
would not want another
split)
- In my eyes, it is certainly a nice feature, but it is not
the first in my personal list of priorities for after 3.2. I
would support it if it would be done, but I would not do
it myself.
Because I would chance our torque environment to 3.2 after
you've released it, I would also change the templates again
to use them with Java5. So it would be a clear start for me
and no problem to submit it back to you.
But I don't have such a complex test environment. We use only
the Object and Peer Templates. So I don't know, if it is
possible to change the Manager to Java5. Do you've a
documentation, which discribes, what you're testing?
bye
Thoralf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
