Client-side validation extensions

I'd like to add a couple of hooks into the client-side, non-Ajax validation code to make it easier (possible?) to call custom JavaScript validators. My current solution seems a bit stop-gappy, but ultimately might be flexible enough to suffice. ObCaveat: I've only looked at the "xhtml" theme so

Re: ur.includeParams to none?

--- On Sat, 9/6/08, Rene Gielen wrote: > Just remeber to file a jira issue with correct "fix for" > tags, then is will be automatically in the release notes > for those releases Cool; thanks. Dave - To unsubscribe, e-mail: [E

Re: ur.includeParams to none?

Just remeber to file a jira issue with correct "fix for" tags, then is will be automatically in the release notes for those releases Dave Newton schrieb: > --- On Sat, 9/6/08, Musachy Barroso wrote: >> I think it is a more appropriate default value. +1 (it >> breaks compatibility tho) > > Not as

Re: Other current failures? was: Re: ur.includeParams to none?

More memory issues; ignore. Running out of tuning parameters; thanks OS X JVM 1.5.mumble. :( All to change the "includeParams" default, which has brought along its own fascinating discussion. I may restrict myself to code and documentation changes from now on. --- On Sat, 9/6/08, Dave Newton

Re: Other current failures? was: Re: ur.includeParams to none?

(Neglected to mention this is on the STRUTS_2_0_X branch; wanted to put the includeParams change there as well.) --- On Sat, 9/6/08, Dave Newton wrote: > Is anybody else seeing these test failures? > > testEnumList(org.apache.struts2.views.jsp.ui.SelectTest) > testMultipleOff(org.apache.struts2.

Other current failures? was: Re: ur.includeParams to none?

Is anybody else seeing these test failures? testEnumList(org.apache.struts2.views.jsp.ui.SelectTest) testMultipleOff(org.apache.struts2.views.jsp.ui.SelectTest) testGenericXhtml(org.apache.struts2.views.jsp.ui.SelectTest) setUp(org.apache.struts2.views.jsp.ui.SelectTest) setUp(org.apache

Re: ur.includeParams to none?

Pah; my bad--wrong button. I just broke the build, fixing. Sorry. --- On Sat, 9/6/08, Dave Newton <[EMAIL PROTECTED]> wrote: > From: Dave Newton <[EMAIL PROTECTED]> > Subject: Re: ur.includeParams to none? > To: "Struts Developers List" > Date: Saturday, September 6, 2008, 10:15 AM > --- On Sat

Re: ur.includeParams to none?

--- On Sat, 9/6/08, Musachy Barroso wrote: > I think it is a more appropriate default value. +1 (it > breaks compatibility tho) Not as bad as the EL thing ;) How are release notes created? Is it just a wiki page? I'll add it to that and update the relevant wiki docs. Dave

Re: ur.includeParams to none?

I think it is a more appropriate default value. +1 (it breaks compatibility tho) On Sat, Sep 6, 2008 at 8:22 AM, Dave Newton <[EMAIL PROTECTED]> wrote: > Anybody care if I change the default to "none"? I'm tired of people > complaining about it because reading the documentation is too hard. > > D

Spring constants in default.properties

Is it necessary that the Spring constants be in default.properties, or can they be in the Spring plugin's config? Just seems a bit weird. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

ur.includeParams to none?

Anybody care if I change the default to "none"? I'm tired of people complaining about it because reading the documentation is too hard. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PR

Re: Struts2 maven archetypes are missing from repo

Lukasz Lenart wrote: > > If someone is interested in, I've prepared some test archetype base on > struts2-archetype-blank sources, it's available here (use -U to update > archetype plugin): > > mvn archetype:generate -DarchetypeCatalog=http://www.lenart.org.pl/maven > > If it will be ok, I wil