Re: Fielderrors tag and the simple theme

I wouldn't have even thought of using the tags for non-HTML-related work; they're form tags. I'd use the collection directly; much cleaner and easier to understand, or I'd expose it as serialized JSON. Everything looks like a thumb when tags are your hammer. Dave On Tue, Apr 19, 2011 at 1:49 PM

RE: Fielderrors tag and the simple theme

> -Original Message- > From: Dave Newton [mailto:davelnew...@gmail.com] > Sent: Tuesday, April 19, 2011 13:02 > To: Struts Developers List > Subject: Re: Fielderrors tag and the simple theme > > Fields can have multiple errors; I'm assuming the list-always > thing is to handle both sing

Re: Fielderrors tag and the simple theme

Since there's nothing stopping you from setting more than one error on a field, it kind of needs to support that use case. (*Chris*) On Apr 19, 2011 9:55 AM, "Jason Pyeron" wrote: > I have been lementing how the fielderror tag forces a list around even when it > is called as > > Does anyone hav

Re: Fielderrors tag and the simple theme

Fields can have multiple errors; I'm assuming the list-always thing is to handle both single and multiple errors in the same way. That said, with reasonable CSS, shouldn't be an issue, no? Dave On Tue, Apr 19, 2011 at 12:54 PM, Jason Pyeron wrote: > I have been lementing how the fielderror tag f

Fielderrors tag and the simple theme

I have been lementing how the fielderror tag forces a list around even when it is called as Does anyone have some comments about why this is good or if not how it should perform? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -

RE: Whitespace issue in tag template [WW-3607]

No, thank you. jpyeron@phoenix /projects/struts/struts2/trunk/core $ svn up Gsrc/main/resources/template/simple/checkbox.ftl Updated to revision 1095120. > -Original Message- > From: Maurizio Cucchiara [mailto:maurizio.cucchi...@gmail.com] > Sent: Tuesday, April 19, 2011 11:22 > To

Re: Whitespace issue in tag template [WW-3607]

Patch applied, thanks Jason On 19 April 2011 16:51, Jason Pyeron wrote: > Could someone review / commit this? I have tested it. > > https://issues.apache.org/jira/browse/WW-3607 > > Thanks > > > -- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > -                            

Whitespace issue in tag template [WW-3607]

Could someone review / commit this? I have tested it. https://issues.apache.org/jira/browse/WW-3607 Thanks -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://ww

RE: Backport policy?

> -Original Message- > From: Wendy Smoak [mailto:wsm...@gmail.com] > Sent: Tuesday, April 19, 2011 9:56 > To: Struts Developers List > Subject: Re: Backport policy? > > On Tue, Apr 19, 2011 at 9:48 AM, Jason Pyeron > wrote: > > > Is there a policy on back porting patches to a given rel

Re: Backport policy?

On Tue, Apr 19, 2011 at 9:48 AM, Jason Pyeron wrote: > Is there a policy on back porting patches to a given release? > > Lets say to the 2.1.8 or 2.1.6 releases? Well, once a release is done, it won't be changed. I see there is a 2.1.8.1 release, so some minor change must have gone in after 2.1

Backport policy?

Is there a policy on back porting patches to a given release? Lets say to the 2.1.8 or 2.1.6 releases? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdin