We did discuss migration at some length and the consensus seemed to be that we would attempt to maintain compatibility with 1.3 where possible but that for compelling new features that there would be some migration required. In particular the areas of config files and expression language were discussed.
The expression language discussion became fairly convoluted so I'll attempt to give you my recollection from about 2 in the morning. Others may jump in and correct me. The expression language syntax will be changing to the OGNL syntax although this is not a radical change. In particular foo/bar will become foo.bar and the .. construct becomes something else weird. The intention was to provide some sort of migration tool either at runtime so old pages/templates/reports would work or as a static once off conversion tool. The release date for webwork on top of xwork (2 products) was estimated at somewhere between 3 and 6 months from now with strong interest in making it 3 months and not 6. Obviously the choice is up to you but I would say that the migration effort shouldn't be too onerous. On Fri, 2003-02-07 at 13:01, Kelvin Tan wrote: > Uh, this question is obviously pre-mature, but I can't keep it down. > > Is there any indication of a proposed date for initial release for xwork? > What's the recommendation for someone planning to start using webwork? hold out > for xwork, or jump in and use webwork as it is now and look to migrate (faint!) > later? In other words, was there any mention of backwards compatibility and/or > migration path... > > KT > -- Peter Kelley <[EMAIL PROTECTED]> Moveit Pty Ltd ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
