: LookupDispatchAction default
unspecified() is the method you want look at the javadoc.
you do need the method name though
/admin/list.do?method
I saw that using submit as the parameter name causes problems so i
wouldn't use that.
On 24 Mar 2004, at 15:16, Brian Sayatovic/AMIG wrote:
I'd like to be able
Mailing List [EMAIL PROTECTED]
cc:
Subject:Re: LookupDispatchAction default
unspecified() is the method you want look at the javadoc.
you do need the method name though
/admin/list.do?method
I saw that using submit as the parameter name causes problems so i
wouldn't use
/2004 08:51 AM
Please respond to Struts Users Mailing List
To: Struts Users Mailing List [EMAIL PROTECTED]
cc:
Subject:Re: LookupDispatchAction default
Look at the sourc for LookupDispatchAction snippet below:
public ActionForward execute(
ActionMapping
PROTECTED]
cc:
Subject:Re: LookupDispatchAction default
unspecified() is the method you want look at the javadoc.
you do need the method name though
/admin/list.do?method
I saw that using submit as the parameter name causes problems so i
wouldn't use that.
On 24 Mar 2004
From: Brian Sayatovic/AMIG [mailto:[EMAIL PROTECTED]
That's exactly my point.
If there is no submit=xxx parameter/value to the action,
then it throws
a NullPointerException. So my action works like this:
/admin/list.do?submit=Refresh
But not like this:
/admin/list.do
unspecified() is the method you want look at the javadoc.
you do need the method name though
/admin/list.do?method
I saw that using submit as the parameter name causes problems so i
wouldn't use that.
On 24 Mar 2004, at 15:16, Brian Sayatovic/AMIG wrote:
I'd like to be able to have someone
From: Brian Sayatovic/AMIG [mailto:[EMAIL PROTECTED]
I'd like to be able to have someone hit my action,
/admin/list.do, without having to specify a submit paramater.
Is there another way to do this? Is it worth suggesting that
LookupDispatchAction support a default or null mapping?
I'm
From: Mark Lowe [mailto:[EMAIL PROTECTED]
unspecified() is the method you want look at the javadoc.
you do need the method name though
/admin/list.do?method
I saw that using submit as the parameter name causes problems so i
wouldn't use that.
I agree about not using submit, if you end up
I agree about not using submit, if you end up needing to use JavaScript
to change the value, you run into problems since submit() is already
function. Calling either document.forms[0].submit.value=something or
document.forms[0].submit() gives an error, I can't remember which. Bad
idea, avoid it.
From: Mark Lowe [mailto:[EMAIL PROTECTED]
It was you post on the thread last week where i pick it up.
Sorry, I'm apparently repeating myself! I can't remember last week this
early in the morning.
Good to know that its been addressed, but I'm on whatever the stable
release of 1.1 is. I'd
On 24 Mar 2004, at 16:13, Wendy Smoak wrote:
From: Mark Lowe [mailto:[EMAIL PROTECTED]
It was you post on the thread last week where i pick it up.
Sorry, I'm apparently repeating myself! I can't remember last week
this
early in the morning.
Good to know that its been addressed, but I'm on
Danny Mui wrote:
I extended the dispatch action to do something like that:
in execute() {
ActionForward forward = null;
if (mapping.getParameter() == null ||
.equals(mapping.getParameter())) {
forward = executeAction(mapping, form, request, response);
} else {
Sorry to have muddled the waters too much, I assumed too much...Having
looked at the LookupDispatchAction code, I can now make a slightly more
educated reply ;).
Yeah I think you're going to have to workaround the parent method.
public class DefaultLookup extends LookupDispatchAction {
I extended the dispatch action to do something like that:
in execute() {
ActionForward forward = null;
if (mapping.getParameter() == null ||
.equals(mapping.getParameter())) {
forward = executeAction(mapping, form, request, response);
} else {
14 matches
Mail list logo
