2.2 and Torque

[Jason van Zyl <jv...@apache.org>]

Hi,

I'm just trying out the new TDK with the 2.2 sample app and there's a couple
glitches using the new Torque but because the use of peers is so rudimentary
in the TDK sample app I'm sure what the impact of using the new Torque code.

If it is a simple matter of requiring people to regenerate their peers than
I can live with that. If it is going to require source code changes than we
should discuss this on the user list because I imagine people will
rightfully get pissed if we make them dig around to make their existing code
work.

There are definite benefits to using the new Torque code because maintenance
will be much simpler and creating extended users will be dead simple.

Jeff Brekke is going to send me a 2.1 app that makes extensive use of peers
and I'm going to see what happens when the new Torque is used with it.

If people accept a regeneration and possible the running of a script to
change some import statements than maybe we can get away with using the new
Torque code in 2.x. If not than we're going to have to roll back the use of
the new Torque code in 2.x. I would rather not do this but I think we have
enough users now that this could be a major inconvenience.

If we can use the new Torque code in 2.x than we could probably also get rid
of torque code in the turbine 2.x repository.

If anyone has already tried to use the new torque code in a 2.x application
I would like to hear about your experiences. I don't want to force people to
use the new Torque code if it doesn't make practical sense to do so.

Thoughts?

-- 

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: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org

Re: 2.2 and Torque

[Jon Stevens <jo...@latchkey.com>]

on 9/7/01 1:11 PM, "Jason van Zyl" <jv...@apache.org> wrote:

> Thoughts?

If I recall correctly, the changes are:

Xml file:
    native instead of autoincrement/sequence

Source code:
    import fixes
    re-generation of base classes

Other than that, it should work pretty well. I'm still wanting to get a
Vector->List change in there that will cause some headaches for people (ie:
now you may have to add a cast and fix imports), but I haven't gotten to it
yet.

thanks,

-jon


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