I count not help myself not to ask the queston and still wonder why it was decided to build struts 2 on XWork instead of directing the effort to come up with struts 2 using something home grown technologies like Command chains ( that is currently used in struts 1.3 +). It makes u wonder what happens if XWORK for some reason or other goes out of commission and there are no releases. I do not see how struts 2 and xwork can be considered a merge to create a new framework (struts 2) while xwork is an independant and fully functional framework (when there is a merge, the merge results in 1 new entity with merging old entities are gone)
I have been an avid user of struts 1 for past few years and have switched to struts 2 to keep up with struts hype but I have not been able to run any project in my case on Websphere (except 2.0.11) with any struts 2 release. Struts 1 used to run like charm. regards, ----- Original Message ---- From: Rene Gielen <[EMAIL PROTECTED]> To: Struts Developers List <dev@struts.apache.org> Sent: Saturday, November 15, 2008 4:22:01 AM Subject: Re: Struts2 and production apps I totally agree that this is currently a very bad situation. Jeromy's tip for static resources is a working fix for the 2.0.12 issue, as well as an uprgade to 2.0.13 testing version would be (this was no GA release). Please note that we fixed the static resource bug immediately when it was reported, and triggered the 2.0.13 build - but since there is still the conversion message issue, it will not become GA. For the needed 2.0.14, we are simply waiting on XWork to be released, because the said conversion error problem is not a Struts issue. The bug was fixed in XWork code immediately after reporting, but XWork has it's own release cycle. That's why it is not in our hand to get out a Struts 2.0.14 release candidate, which technically will be nothing more than a 2.0.13 with a current XWork build. I really hope that we will be getting a XWork release this weekend, and as soon as it is published, be sure that a 2.0.14 build will pushed out right away. And to all those out there using production apps, please feel invited to participate on the QA review and voting process for new releases with reporting integration test results, because that helps us to hunt down the real world issues before we consider a build GA. - René Jeromy Evans schrieb: > Koen Serry wrote: >> * 2.0.12: yes great GA, ah no it doesn't do static resources, so all client >> side validations won't work.... >> > > Just a tip, if you're releasing a production app, you shouldn't be serving > static resources from the struts2 dispatcher. Extract them and the problem > is avoided. > > http://struts.apache.org/2.0.12/docs/performance-tuning.html > http://cwiki.apache.org/S2WIKI/creating-a-custom-dojo-profile-for-struts-20x.html > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
