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]
