> > I think that users will be very > > hesitant to move to a new version of Turbine if the > development effort > > is very high. > > I'm shooting for as close to zero code changes as possible.
Can you give us any idea about the use of Torque in Turbine 2.2/2.3 apps and how that will work in Summit ? Most current Turbine apps heavily rely on Torque object models. I have very briefly looked at the Persister component in the plexus repo but it looked far from complete and only applies to OJB. Do you plan to support the use of Torque in some way ? I have been thinking about Torque + Avalon for a while now and I don't see a clear way of getting rid of the extremely static nature of Torque without a complete redesign (for which I have no time). The only thing I can think off (and which I will hopefully get around to doing this week) is writing a simple Avalon wrapper that only makes sure the static Torque gets configured and initialized. This hardly seems compatible with the Avalon way of things :( Age --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
