On 12/4/05, Don Brown <[EMAIL PROTECTED]> wrote: > I'd classify all those goals as those of approach 1, which is building > 1.x support right in Ti.
Building the support for obsolete framework right into the new framework? No, this is a no go. > My approach #2, to include 1.x jars and develop co-existing tools, lets > someone run a 1.x app "on" Struts Ti completely unchanged and with 100% > functionality, 1.x quirks and all. VDM-like thing? This is a good solution in terms of that (1) it allows to run Struts apps unchanged and (2) it can be removed pretty easily in the future. But I don't see any reason for a user/developer who is pretty happy with Struts 1.x app to upgrade to 2.0. What to upgrade here? I suggest extending the second option with INT 0x71 kind of thing, that is to provide additional services to Struts 1.x apps like Windows 95 provides LFN support for DOS programs. Of course, extended features must be supported both for old-style Struts 1.x apps as well as for new Ti apps, so people would not have to change code twice. This approach may justify trying new features in existing Struts 1.x code, it will also justify upgrade from the managers' perspective. I know that very few DOS apps used extended DOS services, but I think that with Struts the situation will be different. Just add better conversion/validation support and see people jump on it ;-) For example, I find the idea of dynaforms, mirroring the business object, quite appealing. Business object has strongly-typed properties, dynaform would have String-type properties and serve as a UI-buffer for retries and for redisplaying data, when a user chooses session scope for a form. It will also store combobox lists and other reference data, which is not strictly business data. I think Hubert can say something on the topic. This would be a feature worth upgrading, and because it would be provided in Ti only, people would have to upgrade to Ti. Then they would start to explore other features. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
