RE: Validator with Map-backed forms

[Mohan Radhakrishnan]

Hi,
I am opening a javascsript window like this.



This action should only forward to a JSP. The real action is fired only
after one hits the submit button. I know that x.action is some sort of relay
action. How can I specify a relay action as the location of a javascript
window?

 I also know that the following is possible.


   

Thanks,
Mohan

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Validator with Map-backed forms

[Arik Levin ( Tikal )]

You've got it.
I'm working with the commons-validator, it's working just fine.


-Original Message-
From: Darren Spurgeon [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, January 09, 2003 4:05 AM
To: Struts Users Mailing List
Subject: Re: Validator with Map-backed forms

Max-

My team is in the same situation.  Our current problem
is in dealing with over 170 customized forms, which
will balloon to about five times that amount in the
coming year.  Damn those salesmen and their
non-standard accounts! ;) But I digress...

Unfortunately, I don't have an elegant solution.  I
ended up developing a small set of beans to represent
a typical (HTML) form, containing a model for a form,
field pages, field groups, and individual fields. 
Actually, the concept was first used in a piece of
survey software, but it remained portable for other
uses.  I use Commons Digester to parse XML
configuration files (loaded from a database)
representing each form and populate that model as the
application/user requests them.  Actions call a thin
business layer, which uses the custom form model and
performs the validations there.

When the application was moved to a Struts-based one,
I used Map-backed forms to handle the forms and had to
develop a few validation beans to perform the
validation.  Our validations are simple, so it's not
too big a deal.

My thinking now is much like yours--somehow use
Commons Validator, as in building the necessary
formsets programmatically.  As yet, I haven't had the
opportunity to experiment, but I believe that approach
is probably the best current answer.

Please, please, please...Let us all know if you have
any luck, and I'll do the same.

Cheers,
Darren


--- Max Kremer <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I've asked this question before but so far haven't
> received any feedback on
> this subject:
> Is there any way to use the Validator with
> map-backed Action Forms?
> 
> I'm currently using Map-backed forms to manage forms
> that are dynamically
> created from a database, where the number of fields,
> their names, their
> types are not necessarily known at deployment (so no
> DynaActionForm). I'm
> wondering if it's still possible to use the
> (Commons) Validator to validate
> the form fields.
> 
> I understand that the normal usage requires form
> elements in the
> validator-rules file to match that of a form-bean
> element in the Struts
> config file. That's not really possible in my case
> because I don't know
> ahead of time what the fields will be (by name or
> type, in number, etc.).
> Would it be possible to programmatically create the
> formset and form
> elements Validator requires but still use them in
> conjunction with the
> validations file (where the validator elements are
> stored), which would be
> commonly shared between forms? Any pointers on how I
> can accomplish this?
> Or, is there a better way to handle dynamic (i.e.,
> on-the-fly or real-time)
> form creation with Struts?
> 
> 
> 
> 
> 
> 
> 
> Regards,
> 
> Max Kremer
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 


__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Validator with Map-backed forms

[Darren Spurgeon]

Max-

My team is in the same situation.  Our current problem
is in dealing with over 170 customized forms, which
will balloon to about five times that amount in the
coming year.  Damn those salesmen and their
non-standard accounts! ;) But I digress...

Unfortunately, I don't have an elegant solution.  I
ended up developing a small set of beans to represent
a typical (HTML) form, containing a model for a form,
field pages, field groups, and individual fields. 
Actually, the concept was first used in a piece of
survey software, but it remained portable for other
uses.  I use Commons Digester to parse XML
configuration files (loaded from a database)
representing each form and populate that model as the
application/user requests them.  Actions call a thin
business layer, which uses the custom form model and
performs the validations there.

When the application was moved to a Struts-based one,
I used Map-backed forms to handle the forms and had to
develop a few validation beans to perform the
validation.  Our validations are simple, so it's not
too big a deal.

My thinking now is much like yours--somehow use
Commons Validator, as in building the necessary
formsets programmatically.  As yet, I haven't had the
opportunity to experiment, but I believe that approach
is probably the best current answer.

Please, please, please...Let us all know if you have
any luck, and I'll do the same.

Cheers,
Darren


--- Max Kremer <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I've asked this question before but so far haven't
> received any feedback on
> this subject:
> Is there any way to use the Validator with
> map-backed Action Forms?
> 
> I'm currently using Map-backed forms to manage forms
> that are dynamically
> created from a database, where the number of fields,
> their names, their
> types are not necessarily known at deployment (so no
> DynaActionForm). I'm
> wondering if it's still possible to use the
> (Commons) Validator to validate
> the form fields.
> 
> I understand that the normal usage requires form
> elements in the
> validator-rules file to match that of a form-bean
> element in the Struts
> config file. That's not really possible in my case
> because I don't know
> ahead of time what the fields will be (by name or
> type, in number, etc.).
> Would it be possible to programmatically create the
> formset and form
> elements Validator requires but still use them in
> conjunction with the
> validations file (where the validator elements are
> stored), which would be
> commonly shared between forms? Any pointers on how I
> can accomplish this?
> Or, is there a better way to handle dynamic (i.e.,
> on-the-fly or real-time)
> form creation with Struts?
> 
> 
> 
> 
> 
> 
> 
> Regards,
> 
> Max Kremer
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> 
> For additional commands, e-mail:
> 
> 


__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Validator with Map-backed forms

[Max Kremer]

I wish I could pay but I'm broke. However, if had the cash I would
millions  $$$ :-)

But if you could help I would be most grateful.

- Original Message -
From: "Arik Levin ( Tikal )" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
Sent: Sunday, January 05, 2003 1:50 PM
Subject: RE: Validator with Map-backed forms


> Hi Max Kremer.
> How much you are willing to pay ;)
>
> -Original Message-
> From: Max Kremer [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 05, 2003 8:34 PM
> To: Struts Users Mailing List
> Subject: Validator with Map-backed forms
>
> Hi,
>
> I've asked this question before but so far haven't received any feedback
on
> this subject:
> Is there any way to use the Validator with map-backed Action Forms?
>
> I'm currently using Map-backed forms to manage forms that are dynamically
> created from a database, where the number of fields, their names, their
> types are not necessarily known at deployment (so no DynaActionForm). I'm
> wondering if it's still possible to use the (Commons) Validator to
validate
> the form fields.
>
> I understand that the normal usage requires form elements in the
> validator-rules file to match that of a form-bean element in the Struts
> config file. That's not really possible in my case because I don't know
> ahead of time what the fields will be (by name or type, in number, etc.).
> Would it be possible to programmatically create the formset and form
> elements Validator requires but still use them in conjunction with the
> validations file (where the validator elements are stored), which would be
> commonly shared between forms? Any pointers on how I can accomplish this?
> Or, is there a better way to handle dynamic (i.e., on-the-fly or
real-time)
> form creation with Struts?
>
>
>
>
>
>
>
> Regards,
>
> Max Kremer
>
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
> -
>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Validator with Map-backed forms

[Arik Levin ( Tikal )]

Hi Max Kremer.
How much you are willing to pay ;)

-Original Message-
From: Max Kremer [mailto:[EMAIL PROTECTED]] 
Sent: Sunday, January 05, 2003 8:34 PM
To: Struts Users Mailing List
Subject: Validator with Map-backed forms

Hi,

I've asked this question before but so far haven't received any feedback on
this subject:
Is there any way to use the Validator with map-backed Action Forms?

I'm currently using Map-backed forms to manage forms that are dynamically
created from a database, where the number of fields, their names, their
types are not necessarily known at deployment (so no DynaActionForm). I'm
wondering if it's still possible to use the (Commons) Validator to validate
the form fields.

I understand that the normal usage requires form elements in the
validator-rules file to match that of a form-bean element in the Struts
config file. That's not really possible in my case because I don't know
ahead of time what the fields will be (by name or type, in number, etc.).
Would it be possible to programmatically create the formset and form
elements Validator requires but still use them in conjunction with the
validations file (where the validator elements are stored), which would be
commonly shared between forms? Any pointers on how I can accomplish this?
Or, is there a better way to handle dynamic (i.e., on-the-fly or real-time)
form creation with Struts?







Regards,

Max Kremer




--
To unsubscribe, e-mail:

For additional commands, e-mail:



--
To unsubscribe, e-mail:   
For additional commands, e-mail: