ge-
From: Dakota Jack [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 29, 2005 8:25 AM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: Re: DispatchAction defaults
For what it is worth, I agree wholeheartedly with Rick, that this use
of "unspecified(...)" is not wise. If
For what it is worth, I agree wholeheartedly with Rick, that this use
of "unspecified(...)" is not wise. If you want a default method, call
it "default(...)" and leave unspecified(...) as it is.
Jack
--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~
---
Rick Reumann wrote:
Nic Werner wrote the following on 3/28/2005 1:06 PM:
I view the unspecified() method as the equivalent to 'index.jsp'. I
deliberately put an index.jsp (or html) in the directory to provide
the correct output, as opposed to leaving it unhandled - I see Struts
and unspecified()
Nic Werner wrote the following on 3/28/2005 1:06 PM:
I view the unspecified() method as the equivalent to 'index.jsp'. I
deliberately put an index.jsp (or html) in the directory to provide the
correct output, as opposed to leaving it unhandled - I see Struts and
unspecified() as a mirror of this
I view the unspecified() method as the equivalent to 'index.jsp'. I
deliberately put an index.jsp (or html) in the directory to provide the
correct output, as opposed to leaving it unhandled - I see Struts and
unspecified() as a mirror of this.
- Nic.
Rick Reumann wrote:
nitin dubey wrote the f
nitin dubey wrote the following on 3/28/2005 4:43 AM:
The problem I am facing is my unspecified() is always
giving me a null ActionForm object.
As others have mentioned, I'm not fan of providing an unspecified()
dispatch method. I like to always make sure I provide the exact dispatch
parameter as
I think that's the one she was referring to, and apparently it was
exactly what he needed ;)
Dakota Jack wrote:
Not sure what you mean here, but there is an "unspecified" method for
methods that are unspecified.
Jack
On Sun, 27 Mar 2005 08:57:39 -0800, Nic Werner <[EMAIL PROTECTED]> wrote:
Tha
That's what I am trying to do in my application. I
know this works. You can have the code to load the
form in the same Action as unspecified method. When
you use the .do directly in URL it will hit the
unspecified method. Then in the unspecified method
you can pre-populate the action form and t
Not sure what you mean here, but there is an "unspecified" method for
methods that are unspecified.
Jack
On Sun, 27 Mar 2005 08:57:39 -0800, Nic Werner <[EMAIL PROTECTED]> wrote:
> That was exactly what I needed, thanks Wendy.
>
> Wendy Smoak wrote:
>
> > From: "Nic Werner" <[EMAIL PROTECTED]>
That was exactly what I needed, thanks Wendy.
Wendy Smoak wrote:
From: "Nic Werner" <[EMAIL PROTECTED]>
I call this with: addDevice.do?method=edit
and: addDevice.do?method=update
The param for the first page seems a bit extraneous, is there a way
that DispatchAction can just call a default method
Hello Nic,
I may be over simplyfing the problem but why not just set the default value
of the dispath hidden field [what ever that may be i.e. in your case method]
in the form to the default value that you wanted insted of the default null.
Anyhow, in case I was over simplifing the problem her
From: "Nic Werner" <[EMAIL PROTECTED]>
I call this with: addDevice.do?method=edit
and: addDevice.do?method=update
The param for the first page seems a bit extraneous, is there a way that
DispatchAction can just call a default method if the param isn't
specified? I would like to just call: addDevi
12 matches
Mail list logo
