[OS-webwork] how about returning invalid.token result only when the token tag is used

anyone else think it would make sense to return the invalid.token result only when the token tag is used on a form? that way i could just put the token interceptor in my default stack and just use the token functionality on any of my forms by using the token tag

Re: [OS-webwork] Passing Iterator's value

On Thu, Sep 18, 2003 at 11:12:38PM +0200, Hendrik van der Linde wrote: Which version are you using? I'm talking about CVS head... I am using HEAD: bash hendrik ~/Documents/programmeren/extern/webwork2 % cvs status -v build.xml

RE: [OS-webwork] how about returning invalid.token result only when the token tag is used

I believe the change Matt made to the TokenInterceptor to make the validToken() method return what the Javadoc said it should will make this possible (this is in CVS HEAD). I think :-) I still need to go in and fix the TokenInterceptorTest to pass (bad Matt ;-)) so don't hold me to anything I've

[OS-webwork] grouping textfields (ui tags)

Title: grouping textfields (ui tags) Hi all, I'm trying to build a form that contains a 'telephone' field. In plain HTML, it would look like something like this: --- tr td colspan=2 class=errorspan class=errorMessagePlease fill in the area code and phone number./span/td /tr tr td

Re: [OS-webwork] hibernate/webwork2 best practices

any update on when this code will be shared with us? (can you tell im anxious? :) Pat Lightbody wrote: Glad you like it! Spread the word :) I've used Hibernate + WebWork2 in a couple projects, and I always used the design that spawned from our (Mike/Joe/Ara/Mine) upcoming book that involves

RE: [OS-webwork] formbean vs. action

OK.. I like the sound of that ProhibitedFieldValidator :) Would it be possible, and a good idea to allow parameterization of interceptors that are on a particular stack, using the below technique ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason

RE: [OS-webwork] formbean vs. action

I'm not sure how possible that would be... Actually, I'm relatively certain that it would be difficult... It might be a feature we could add with Xwork 1.1 when we rewrite the configuration API to actually be runtime programmatically changeable... -Original Message- From: Cameron Braid

Re: [OS-webwork] how about returning invalid.token result only when the token tag is used

on second thought about this is better to leave as is if not someone could hack the page to not use the token and resubmit it multiple times Jason Carreira wrote: I believe the change Matt made to the TokenInterceptor to make the validToken() method return what the Javadoc said it should will

Re: [OS-webwork] formbean vs. action

- Wiadomosc oryginalna - Od: Jason Carreira [EMAIL PROTECTED] Do: [EMAIL PROTECTED] Wyslano: 18 wrzesnia 03 18:37 Temat: RE: [OS-webwork] formbean vs. action That's true, but you could check the param map and see if there's anything not allowed in there and add errors... Which, with

[OS-webwork] cvs head test failing

latest cvs check is failing the unit tests, [junit] - Standard Error - [junit] 0 [main] WARN util.TokenHelper - Could not find token name in params. [junit] - --- [junit] Testcase:

Re: [OS-webwork] formbean vs. action

On 9/18/03 8:25 PM, Cameron Braid [EMAIL PROTECTED] wrote: OK.. I like the sound of that ProhibitedFieldValidator :) Would it be possible, and a good idea to allow parameterization of interceptors that are on a particular stack, using the below technique ? I've been meaning to dig and

RE: [OS-webwork] formbean vs. action

I would rather not try to make ParametersInterceptor do too much... Setting properties is enough. And no... no 1.4 dependencies, 1.3 only. -Original Message- From: Michal Mosiewicz [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 5:31 AM To: [EMAIL PROTECTED] Subject: