> And ... what happend to 1.2.1 as far as a > download link from an html page with due note as to release level > (red/yellow/orange)).
All this has been done. http://struts.apache.org/acquiring.html We don't color-code our releases, but the levels we do use are mentioned. Before GA goes final, we need a proper download.cgi page. But (first things first) the rest the infrastructure we need is in place and documented. http://struts.apache.org/releases.html On Sat, 17 Jul 2004 20:31:20 -0500, Vic Cekvenich wrote: > I think there should be support for RiA and SoA in the new > "request" processor, which is what the chain enables. > Not many new HTML/HTTP apps will be constructed in '05 to be > operated in '06, '07. Right now, we discussing infrastructure. This item (and the others) is another topic: what we are going to do once the infrastructure is in place. Since our bandwidth is limited, let's keep the focus on infrastructure for now. And speaking of bandwidth, I hear the church bells ringing .. so I'm off. -Ted. > So one could get a SOAP or similar type request and not have to > refactor. I think that should be the main goal, have it work with > RiA/SoA 1st and then look for a way how to make it backaward > compatiable and support legacy html/html apps (since that is well > known how those work). > > At worst, make an interface or mechanisam so that people can > implement a protocol. > > (Also perform() got removed and Struts is still to mark beans and > logic for depecation. And it be nice that a nightly build ships > with a sample chain. And ... what happend to 1.2.1 as far as a > download link from an html page with due note as to release level > (red/yellow/orange)). > > > .V --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
