[S2] parseWidgets should be false for better performance!

Hi guys, I'm thinking about open an issue to make put parseWidgets: false on djConfig initial load. This would improve the performance so much. The fact is that dojo walk through each DOM node in a document looking for widgets to parse, so it makes the footprint very slow. The solution is to tel

Re: [S2] parseWidgets should be false for better performance!

Sounds fair enough. The best way to get something like this implemented though is to provide a patch for the fixes and attach it to the JIRA ticket. james On Fri Jul 27 9:05 , Felipe Rodrigues <[EMAIL PROTECTED]> sent: > >Hi guys, > >I'm thinking about open an issue to make put parseWidgets:

about adding #action to context

Is there any reason why adding a "#action" to the context (https://issues.apache.org/struts/browse/WW-2034) pointing to the last executed action would be a bad idea? It seems so obvious that I feel like I'm missing something :) musachy -- "Hey you! Would you help me to carry the stone?" Pink Fl

[OSS Bamboo] Struts 2 SVN - Main Build build 417 has FAILED (2 tests failed). Change made by musachy

The project Struts 2 SVN - Main Build has the following 2 changes by 1 author: *musachy* made the following changes at Comment: WW-2050 Separate JSONValidationInterceptor from AnnotationValidationInterceptor Patch provided by Lukasz Racon > /struts/struts2/trunk/core/src/main/java/org/apache/st

[OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 73 has FAILED (2 tests failed). Change made by musachy

The project Struts 2 SVN - Main Build (Java 6) has the following 3 changes by 1 author: *musachy* made the following changes at Comment: WW-2050 Separate JSONValidationInterceptor from AnnotationValidationInterceptor Patch provided by Lukasz Racon > /struts/struts2/trunk/core/src/main/java/org

[OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 74 has FAILED (2 tests failed, no failures were new). Change made by musachy

The project Struts 2 SVN - Main Build (Java 6) has the following 1 change by 1 author: *musachy* made the following changes at Comment: Update tag description > /struts/struts2/trunk/core/src/main/java/org/apache/struts2/components/Div.java > (560334) --

[OSS Bamboo] Struts 2 SVN - Main Build build 418 has FAILED (2 tests failed, no failures were new). Change made by musachy

The project Struts 2 SVN - Main Build has the following 2 changes by 1 author: *musachy* made the following changes at Comment: WW-2050 Separate JSONValidationInterceptor from AnnotationValidationInterceptor Patch provided by Lukasz Racon > /struts/struts2/trunk/plugins/dojo/src/main/resources/

[OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 75 was SUCCESSFUL (with 696 tests). Change made by musachy

The project Struts 2 SVN - Main Build (Java 6) has the following 1 change by 1 author: *musachy* made the following changes at Comment: WW-2050 Separate JSONValidationInterceptor from AnnotationValidationInterceptor Patch provided by Lukasz Racon > /struts/struts2/trunk/core/src/test/java/org/

[OSS Bamboo] Struts 2 SVN - Main Build build 419 was SUCCESSFUL (with 696 tests). Change made by musachy

The project Struts 2 SVN - Main Build has the following 1 change by 1 author: *musachy* made the following changes at Comment: WW-2050 Separate JSONValidationInterceptor from AnnotationValidationInterceptor Patch provided by Lukasz Racon > /struts/struts2/trunk/core/src/test/java/org/apache/str

Missing project information and reports in site

Hi developers :-) Do you know if there is a reason why the Struts site does not show Project information and Project reports in any place? Is it a bug? The reason is that some people (like me) is used to see these information in the same place. Thanks Antonio -

Voting Process (was Re: Struts 2.0.9 release (was Re: S2 security fix release planning (XWork 2.0.4 is out)))

On 7/23/07, Ted Husted <[EMAIL PROTECTED]> wrote: > In the interest of time, I would like to declare a quality grade on > Struts 2.0.9 AS SOON AS we have received three binding votes toward > one of the grades, and NOT WAIT the usual 72 hours! I only just saw this - so basically this vote was e

Re: Voting Process (was Re: Struts 2.0.9 release (was Re: S2 security fix release planning (XWork 2.0.4 is out)))

While I suppose consulting the PMC would have been appropriate, I disagree all votes, no matter what, should be open for 72 hours. In this case, a severe security fix release, we should allow a shorter time. Perhaps that would be 12 or 18 hours, but certainly no more than 24. Just because the f