DO NOT REPLY [Bug 20535] - Dynamically size arrays to allow array types in request scope DynaActionForm forms

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: editing wiki docs

Martin Cooper on 23/09/07 18:24, wrote: On 9/23/07, Adam Hardy <[EMAIL PROTECTED]> wrote: Ted Husted on 21/09/07 22:34, wrote: On 9/21/07, Wes Wannemacher <[EMAIL PROTECTED]> wrote: Hello, I recently volunteered to help update some of the struts2 docs. I started poking around on the wiki and

Re: Convention/Annotation Design Patterns (was [s2] Goal - no experimental code in core for 2.1)

On 10/9/07, Ted Husted <[EMAIL PROTECTED]> wrote: > I tagged a version of MailReader Zero that was using a single > namespace and (some) multiple methods at > > * http://sq1-struts2.googlecode.com/svn/tags/mailreader-zero-flat/ > > I've started to refactor the "head" to use multiple namespaces and

Re: Convention/Annotation Design Patterns (was [s2] Goal - no experimental code in core for 2.1)

I tagged a version of MailReader Zero that was using a single namespace and (some) multiple methods at * http://sq1-struts2.googlecode.com/svn/tags/mailreader-zero-flat/ I've started to refactor the "head" to use multiple namespaces and single-method classes, but so far I'm only half done. * h

Re: [s2] Goal - no experimental code in core for 2.1

If we want stable conventions, then we should try to exercise the conventions against more applications, to be sure we're covering the core use cases. I know some of us are trying these with our own applications, but we should also try them with more example applications that we can all review. In