Re: execute instead of get and post

2005-07-07 Thread Rick Reumann
Michael Jouravlev wrote the following on 7/7/2005 5:26 PM: On 7/7/05, Rick Reumann <[EMAIL PROTECTED]> wrote: klute wrote the following on 7/7/2005 3:07 PM: It seems like it would make sense to have both so that you can use GET to set up a particular form and POST to process that form. Inste

Re: execute instead of get and post

2005-07-07 Thread Michael Jouravlev
On 7/7/05, Rick Reumann <[EMAIL PROTECTED]> wrote: > klute wrote the following on 7/7/2005 3:07 PM: > > > It seems like it would make sense to have both so that > > you can use GET to set up a particular form and POST > > to process that form. Instead, I'd have to look at the > > request to see wh

Re: execute instead of get and post

2005-07-07 Thread Rick Reumann
klute wrote the following on 7/7/2005 3:07 PM: It seems like it would make sense to have both so that you can use GET to set up a particular form and POST to process that form. Instead, I'd have to look at the request to see what was invoked and then conditionally do some processing. No need f

execute instead of get and post

2005-07-07 Thread klute
Is there a good reason why Struts does not distinguish between GET and POST requests and tunnels both through execute()? It seems like it would make sense to have both so that you can use GET to set up a particular form and POST to process that form. Instead, I'd have to look at the request to se