AW: Torque with Java5 features
Would you mind to sign a cla and fax it to the ASF office ? see http://www.apache.org/licenses/#clas Yepp, done. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Torque with Java5 features
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]
Re: Torque with Java5 features
We have developed a simple wrapper for Torque that allows integration with
the Spring Framework. By using it, you get some support for Generics.
https://torque-spring.dev.java.net/
Currently we support a simple set of methods.
xxx
package org.springmodules.orm.torque;
import java.util.List;
import org.apache.torque.om.BaseObject;
public interface TorqueExternalOperations extends TorqueOperations {
T extends BaseObject T create(ClassT torqueObjectClass) throws
TorqueSpringException;
T extends BaseObject ListT find(ClassT torqueObjectClass, int[]
ids) throws TorqueSpringException;
T extends BaseObject T find(ClassT torqueObjectClass, int id) throws
TorqueSpringException;
T extends BaseObject void remove(T persistableObject) throws
TorqueSpringException;
T extends BaseObject void save(T persistableObject) throws
TorqueSpringException;
T extends BaseObject T copy(final T object) throws
TorqueSpringException;
}
x
Note this framework it is not replacement for torque
it is just adds extra functionality typical for springframework.
We are looking for reviews/suggestions for expansion/improvement any peer
review would be appreciated.
Torque with Java5 features
Hi!
I'm not sure, if this feature was discussed already on this list, but
how big is the chance, that torque supports the Java5 features, like
generics, in a future version? I know that this means a lot of work and
much trouble with users, who aren't able to use Java5 because of some
restrictions or what ever. But it has some very useful addons. For
example a generated doSelect could return a ListTableA. That makes
runtime errors - because of wrong class casts - obsolete.
After Sun's launch of the Java5 version, I had changed most of the class
generation templates in torque 3.1 (object,peer,map) to use this
features in our whole application without any breakage (til
BasePeer...). That tooks me 4-5 hours and wasn't really complicated. But
it's practically a branch, because older Java compiler aren't able to
compile this generated classes. And I know it's not useful to maintain
two source tree for pre Java5 and Java5.
I think it could be possible to create templates that are able to
generate preJava5 and Java5 version by using a switch in the
configuration. For example a switch called torque.java5, which could be
true or false could be used to output the best java source code. For
example:
public static java.util.List#if($torque.java5)${table.JavaName}#end
doSelect(Criteria criteria) throws org.apache.torque.TorqueException
{
return populateObjects(doSelectVillageRecords(criteria));
}
It's not nice, but it could work. The other part (converting the
generator and the runtime libraries) is another problem...
But for now I'm just asking, if this is on your plan?
bye
Thoralf
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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]
