Re: Multipage forms and validation

2001-06-04 Thread Ted Husted

When the time comes, David's Validation servlet would get my vote.
Unfortunately, we need to get 1.0 out the door before voting on anything
like this. Beta 3 is counting down now, so we only talking a couple of
weeks now.

In any event, what features Struts, or any Jakarta product, will offer
in any timeframe, will always depend on what people contribute. No one
here can say hey you, go implement this feature. What gets implemented
depends on what people choose to contribute, and David has stepped
forward with a very fine contribution. 

One of things that make it a fine contribution is that the Validator
servlet snaps right into the framework, without altering anything else.
So you're free to use it, or not to use it, or to use something else.
Which is as Struts-esque as you can get ;-) So I'd say use it .. I do!

Niall Pemberton wrote:
 
 David,
 
 I see your on the 1.1 ToDo list as a volunteer for Standard Validations
 and Client Side Validations - is it likely your validation framework is
 going to be adopted for Struts - and if so how close is what you're offering
 now to what Struts will have in 1.1?
 
 I'm just wondering whether to plough on with what we've got or wait for what
 might be coming in Struts.
 
 Niall



RE: Multipage forms and validation

2001-06-01 Thread Niall Pemberton

David,

I see your on the 1.1 ToDo list as a volunteer for Standard Validations
and Client Side Validations - is it likely your validation framework is
going to be adopted for Struts - and if so how close is what you're offering
now to what Struts will have in 1.1?

I'm just wondering whether to plough on with what we've got or wait for what
might be coming in Struts.

Niall


 -Original Message-
 From: David Winterfeldt [mailto:[EMAIL PROTECTED]]
 Sent: 31 May 2001 23:32
 To: [EMAIL PROTECTED]
 Subject: Re: Multipage forms and validation


 I've done some work on a validation framework for
 Struts that is based on defining rules in an xml file.
  Right now it depends on associating a field with a
 page and setting a variable in the JSP page to set
 what page you are on.  I had a long discussion with
 someone on how to make it not depend on associating
 fields with a page so it was separated from the view,
 but I haven't had time to finish doing that.  The
 biggest problem is that if you have a session scope
 bean then you still absolutely have to know if there
 is a checkbox field on the page so you can reset it.
 The best idea to get away from page numbers was to
 have a custom ActionForward for each page and pass in
 the checkbox fields to be reset along with the action.

 Here is the url for what I currenty have working.
 There is a multi-page example in the validator.war and
 jdbc-validator.war in the webapps directory.

 http://home.earthlink.net/~dwinterfeldt

 David Winterfeldt

 --- Lukasz Kowalczyk [EMAIL PROTECTED] wrote:
  Hi.
 
  I'm trying to employ Struts to help me build
  multi-page forms.
  Those forms consist of all kinds of inputs,
  including multipart.
 
  The questions are as follows:
 
  1. How can I validate forms which I know will never
  set all of the
  required elements at a time since the required
  elements can span multiple
  pages? I could check which submit was clicked and
  then validate just a
  subset of form elements but I think it's not very
  Struts-oriented, and
  secondly this makes validate() method dependent on
  specific placement of
  form inputs (when I decide to move some field to
  another page I have to
  modify validate()).
 
  2. Can I use the same Action class to handle
  multipart and non-multipart
  request? Will performance hurt because of this?
 
  --
  £ukasz Kowalczyk
 


 __
 Do You Yahoo!?
 Get personalized email addresses from Yahoo! Mail - only $35
 a year!  http://personal.mail.yahoo.com/





RE: Multipage forms and validation

2001-06-01 Thread David Winterfeldt

It hasn't been discussed by the other volunteers and
Struts users/developers exactly what features the
client/standard validations should have.  I'll send an
e-mail to get the discussion started.

David

--- Niall Pemberton [EMAIL PROTECTED]
wrote:
 David,
 
 I see your on the 1.1 ToDo list as a volunteer for
 Standard Validations
 and Client Side Validations - is it likely your
 validation framework is
 going to be adopted for Struts - and if so how close
 is what you're offering
 now to what Struts will have in 1.1?
 
 I'm just wondering whether to plough on with what
 we've got or wait for what
 might be coming in Struts.
 
 Niall
 
 
  -Original Message-
  From: David Winterfeldt
 [mailto:[EMAIL PROTECTED]]
  Sent: 31 May 2001 23:32
  To: [EMAIL PROTECTED]
  Subject: Re: Multipage forms and validation
 
 
  I've done some work on a validation framework for
  Struts that is based on defining rules in an xml
 file.
   Right now it depends on associating a field with
 a
  page and setting a variable in the JSP page to set
  what page you are on.  I had a long discussion
 with
  someone on how to make it not depend on
 associating
  fields with a page so it was separated from the
 view,
  but I haven't had time to finish doing that.  The
  biggest problem is that if you have a session
 scope
  bean then you still absolutely have to know if
 there
  is a checkbox field on the page so you can reset
 it.
  The best idea to get away from page numbers was to
  have a custom ActionForward for each page and pass
 in
  the checkbox fields to be reset along with the
 action.
 
  Here is the url for what I currenty have working.
  There is a multi-page example in the validator.war
 and
  jdbc-validator.war in the webapps directory.
 
  http://home.earthlink.net/~dwinterfeldt
 
  David Winterfeldt
 
  --- Lukasz Kowalczyk [EMAIL PROTECTED]
 wrote:
   Hi.
  
   I'm trying to employ Struts to help me build
   multi-page forms.
   Those forms consist of all kinds of inputs,
   including multipart.
  
   The questions are as follows:
  
   1. How can I validate forms which I know will
 never
   set all of the
   required elements at a time since the required
   elements can span multiple
   pages? I could check which submit was clicked
 and
   then validate just a
   subset of form elements but I think it's not
 very
   Struts-oriented, and
   secondly this makes validate() method dependent
 on
   specific placement of
   form inputs (when I decide to move some field to
   another page I have to
   modify validate()).
  
   2. Can I use the same Action class to handle
   multipart and non-multipart
   request? Will performance hurt because of this?
  
   --
   £ukasz Kowalczyk
  
 
 
  __
  Do You Yahoo!?
  Get personalized email addresses from Yahoo! Mail
 - only $35
  a year!  http://personal.mail.yahoo.com/
 
 


__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/



Re: Multipage forms and validation

2001-05-31 Thread David Winterfeldt

I've done some work on a validation framework for
Struts that is based on defining rules in an xml file.
 Right now it depends on associating a field with a
page and setting a variable in the JSP page to set
what page you are on.  I had a long discussion with
someone on how to make it not depend on associating
fields with a page so it was separated from the view,
but I haven't had time to finish doing that.  The
biggest problem is that if you have a session scope
bean then you still absolutely have to know if there
is a checkbox field on the page so you can reset it. 
The best idea to get away from page numbers was to
have a custom ActionForward for each page and pass in
the checkbox fields to be reset along with the action.

Here is the url for what I currenty have working. 
There is a multi-page example in the validator.war and
jdbc-validator.war in the webapps directory.

http://home.earthlink.net/~dwinterfeldt

David Winterfeldt

--- Lukasz Kowalczyk [EMAIL PROTECTED] wrote:
 Hi.
 
 I'm trying to employ Struts to help me build
 multi-page forms.
 Those forms consist of all kinds of inputs,
 including multipart.
 
 The questions are as follows:
 
 1. How can I validate forms which I know will never
 set all of the
 required elements at a time since the required
 elements can span multiple
 pages? I could check which submit was clicked and
 then validate just a
 subset of form elements but I think it's not very
 Struts-oriented, and
 secondly this makes validate() method dependent on
 specific placement of
 form inputs (when I decide to move some field to
 another page I have to
 modify validate()).
 
 2. Can I use the same Action class to handle
 multipart and non-multipart
 request? Will performance hurt because of this?
 
 -- 
 £ukasz Kowalczyk
 


__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/