Re: Form beans and dispatch actions

2002-05-24 Thread Ted Husted

The mapping is how the ActionServlet knows which ActionForm class to
use. If you do not specify a form-bean in the mapping, then the
controller doesn't use an ActionForm. 

The DispatchAction is called like any other and a form-bean must be
specified in the mapping if one is to be passed to the Action. 

-- Ted Husted, Husted dot Com, Fairport NY US
-- Developing Java Web Applications with Struts
-- Tel: +1 585 737-3463
-- Web: http://husted.com/about/services


[EMAIL PROTECTED] wrote:
> 
> Hi,
> 
> Can someone please tell me if and how I can use DispatchAction and form beans 
>together - i.e. I have a DispatchAction with multiple methods as entry points and 
>different forms for different methods.
> 
> Currently it seems that form are passed in as null to the these methods, and thus I 
>have to interrogate the request parameters in order to obtain the parameter values. 
>However, the form bean does seem to get used - or at least my debug call in the 
>constructor got printed out! Could someone explain exactly what is going on?
> 
> I currently only one action mapping definition for such an action class, without any 
>form attributes set. In order for the form bean to be passed correctly, do I need to 
>create multiple action mapping entries, one per form type?
> 
> Any answers would be much appreciated.
> 
> Cheers,
> 
> Kosh
> 
> Visit our website at http://www.ubswarburg.com
> 
> This message contains confidential information and is intended only
> for the individual named.  If you are not the named addressee you
> should not disseminate, distribute or copy this e-mail.  Please
> notify the sender immediately by e-mail if you have received this
> e-mail by mistake and delete this e-mail from your system.
> 
> E-mail transmission cannot be guaranteed to be secure or error-free
> as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses.  The sender therefore
> does not accept liability for any errors or omissions in the contents
> of this message which arise as a result of e-mail transmission.  If
> verification is required please request a hard-copy version.  This
> message is provided for informational purposes and should not be
> construed as a solicitation or offer to buy or sell any securities or
> related financial instruments.
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 

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




Form beans and dispatch actions

2002-05-24 Thread Kosh . Podder

Hi,

Can someone please tell me if and how I can use DispatchAction and form beans together 
- i.e. I have a DispatchAction with multiple methods as entry points and different 
forms for different methods.

Currently it seems that form are passed in as null to the these methods, and thus I 
have to interrogate the request parameters in order to obtain the parameter values. 
However, the form bean does seem to get used - or at least my debug call in the 
constructor got printed out! Could someone explain exactly what is going on?

I currently only one action mapping definition for such an action class, without any 
form attributes set. In order for the form bean to be passed correctly, do I need to 
create multiple action mapping entries, one per form type?

Any answers would be much appreciated.

Cheers,

Kosh

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


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