this.refreshList(mapping, form, request, response);
}
While the JavaDocs do imply this should work, when I looked in the Struts
1.1 source, the execute method of LookupDispatchAction generates the erorr
message I see as soon as request.getParameter(parameterName) returns null.
In fact, I can find
Look at the sourc for LookupDispatchAction snippet below:
public ActionForward execute(
ActionMapping mapping,
ActionForm form,
HttpServletRequest request,
HttpServletResponse response)
throws Exception {
// Identify the request parameter containing
of
replies suggested I could use 'unspecified', but that didn't work.
So, is the answer:
(a) I should never use the second form because it is evil
(b) I could use the second form but its broken in LookupDispatchAction
(c) something else?
Regards,
Brian.
Mark Shifman [EMAIL PROTECTED]
03/25
,
HttpServletResponse response
) {
return this.refreshList(mapping, form, request,
response);
}
While the JavaDocs do imply this should work, when I looked in the
Struts
1.1 source, the execute method of LookupDispatchAction generates the
erorr
message I see as soon
So, is the answer:
(a) I should never use the second form because it is evil
(b) I could use the second form but its broken in LookupDispatchAction
(c) something else?
What version of Struts are you using? I suspect you're on 1.1 or
something older than a nightly build. The javadocs
I'd like to be able to have someone hit my action, /admin/list.do, without
having to specify a submit paramater. However, the action is a subclass
of LookupDispatchAction whci requires that the request parameter be
supplied. Looking in the struts source code, it would be nice
hit my action, /admin/list.do,
without
having to specify a submit paramater. However, the action is a
subclass
of LookupDispatchAction whci requires that the request parameter be
supplied. Looking in the struts source code, it would be nice if the
LookupDispatchAction could fall back to a default
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
hi struts-users
is it possible to use the LookupDispatchAction with image-submit-buttons
(html:image) instead of normal submit-buttons?
thanks and greetings
stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
take your eyes off the goal.
-Original Message-
From: Stefan Burkard [mailto:[EMAIL PROTECTED]
Sent: Thursday, 18 March 2004 8:19 PM
To: [EMAIL PROTECTED]
Subject: LookupDispatchAction with html:image?
hi struts-users
is it possible to use the LookupDispatchAction with image-submit
Mobile : 98904 25400
An Obstacle is something you see when you take your eyes off the goal.
-Original Message-
From: Stefan Burkard [mailto:[EMAIL PROTECTED]
Sent: Thursday, 18 March 2004 8:19 PM
To: [EMAIL PROTECTED]
Subject: LookupDispatchAction with html:image?
hi struts-users
is it possible
try ImageButtonBeanManager from Mitranosoft
- Original Message -
From: Stefan Burkard [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 2:48 PM
Subject: LookupDispatchAction with html:image?
hi struts-users
is it possible to use the LookupDispatchAction
=profile.dom.upload.label.changeMetaData/
/html:submit
/html:form
# A lookupDispatchAction like this:
public class DomUploadAction extends LookupDispatchAction{
protected Map getKeyMethodMap() {
Map map = new HashMap();
map.put(profile.dom.upload.label.addMetaData, addMetaData);
map.put
to refer to the form element with JavaScript-- there is already
a document.forms[0].submit(); function (method?) and you'll get errors
if you ever try to say document.forms[0].submit.value=abc;
I suggest changing the name of the form element to 'method' as used in
the LookupDispatchAction javadocs
I have been trying to figure out how to handle
a cancel button using LookupDispatchAction.
Specifically, I want to not do form validation
if the cancel button is pressed. I found out from
discussion on this list that the cancel button
ends up with a different name attribute than
other submit
Anybody jump in and say if there's a better way to
do this...
I am attempting to create a simple multistep application
for gathering registration information. Each page will be
validated using the Validator framework. I stumbled across
the LookupDispatchAction and thought it might be useful
/
/
'parameter' is wrong. It should be the name of the request parameter
you want the LookupDispatchAction to use. For example, I use 'mode' or
'userAction' in a couple of my webapps.
The *value* of this request parameter will be compared to the right hand
side of the properties you list
=administratorForm
scope=request
input=/pages/administrator.jsp
parameter=myaction
forward name=admSearchDone path=/pages/administrator.jsp/
/action
...
AdministratorAction:
public class AdministratorAction extends LookupDispatchAction {
protected Map getKeyMethodMap
Søren,
The error message indicates that you are missing a button.search entry in
your Application Resources file.
-Richard
-Original Message-
From: Søren Hjarlvig [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 10, 2004 2:13 PM
To: [EMAIL PROTECTED]
Subject: LookupDispatchAction
From: Yee, Richard K,,DMDCWEST [mailto:[EMAIL PROTECTED]
The error message indicates that you are missing a
button.search entry in
your Application Resources file.
Earlier, Søren wrote:
http://localhost:8080/fonde/administrator.do?myaction=button.search
In addition, the 'myaction'
Wendy Smoak wrote:
In addition, the 'myaction' request parameter should be set to whatever the value of button.search is in ApplicationResources.properties.
ApplicationResources.properties:
button.search=ClickHere
Thank you. This solved my problem :-)
The entry was missing from my
);
}
}
renderForm renders the form (I don't access the jsp directly, just the
action, this way it calls unspecified, which reads data from a database
and populates the form).
I tried converting this to a LookupDispatchAction, making
MyDispatchAction extend LookupDispatchAction and adding
protected Map
Well, LookUpDispatchAction doesn't call the unspecified action when it
is no parameter is supplied.
One way would be to override the method that does the lookup and when no
action parameter is supplied, call the unspecified() parameter.
Another way is to make your initial call to the action
, Jason Lea wrote:
Well, LookUpDispatchAction doesn't call the unspecified action when it
is no parameter is supplied.
One way would be to override the method that does the lookup and when no
action parameter is supplied, call the unspecified() parameter.
Another way is to make your initial
I'm trying to figure out what exactly LookupDispatchAction does, if the
parameter in the url is not present (returned as null). I'm looking at
the source code, and it apparently throws an ServletException if the
returned parameter is null.
I've tried implementing the unspecified method
Dear struts users,
In every webapplication there are links. As I read in Struts in Action,
it's better to make links with actions.
I'm now working on some part of the application where we have to do a lot of
CRUD actions, so I want to use the LookupDispatchAction. Inserting/creating
records
Rotteveel [EMAIL PROTECTED]:
Dear struts users,
In every webapplication there are links. As I read in Struts in Action,
it's better to make links with actions.
I'm now working on some part of the application where we have to do a lot
of
CRUD actions, so I want to use the LookupDispatchAction
Dear struts users,
I'm having some trouble with something I would like to do after a
successfull insert in the database.
I will try to explain it as well as I can.
In our menu we have a link. This link points to an action
/maintenance/createCustomer.do. This action is a ForwardAction and it
From: Ronald Rotteveel [mailto:[EMAIL PROTECTED]
I WOULD LOVE lose the name of the customer that I just inserted.
If I come back to the customer form now, the
field where someone can type a name is already filled with
the name I just inserted.
Sounds like your form bean is in session
Obviously, that was the wrong key...
From: Ronald Rotteveel [mailto:[EMAIL PROTECTED]
I WOULD LOVE lose the name of the customer that I just inserted.
If I come back to the customer form now, the
field where someone can type a name is already filled with
the name I just inserted.
(mapping);
I presume you have written your own?
Anyway, it looks like the reset method isn't called. Could it be that my
LookupDispatchAction isn't implemented well?
Thanks for any submissions in advance!
Regards,
Ronald Rotteveel
- Original Message -
From: Wendy Smoak [EMAIL PROTECTED
values
specified in struts-config. What you've done is fine. (I'd probably
set the values to if they're Strings to avoid NPE's though.)
Anyway, it looks like the reset method isn't called. Could it
be that my LookupDispatchAction isn't implemented well?
Put a log statement at the top of your
I have a very strange Exception, originating in the
LookupDispatchAction. Imagine the
following scenario in a multi-language app: A client browser has a
English (United-Kingdom)
language as first preference, Dutch (nl) as second, and English
(United-states) as third.
When the client
Has anyone ever gotten a LookupDispatchAction to work with more than one
locale? I am simply trying to do a small in english and spanish, all is well
until I hit a lookupdispatchaction. It then uses the translated text as the
method name instead of the map lookup name.
Mike
action class it uses the translated text as the method name so obviously it
doesn't find it. Is there something simple I am missing?
Some basics.
application.properties
button.edit=Edit
application_es_MX.properties
button.edit=NYT
LookupDispatchAction
map.put(button.edit, Edit);
and I have
I thought I might just raise this here because I see struts has
obviously no qualms about submit button functionality, but it bugs me.
I'm not using LookupDispatchAction, but I would like to if it wasn't for
the annoying browser behaviour on submit of the HTML-input submit button
values
Adam Hardy wrote:
I thought I might just raise this here because I see struts has
obviously no qualms about submit button functionality, but it bugs me.
I'm not using LookupDispatchAction, but I would like to if it wasn't
for the annoying browser behaviour on submit of the HTML-input submit
and LookupDispatchAction.
Craig R. McClanahan wrote:
Adam Hardy wrote:
I thought I might just raise this here because I see struts has
obviously no qualms about submit button functionality, but it bugs me.
I'm not using LookupDispatchAction, but I would like to if it wasn't
for the annoying browser behaviour
On 10/08/2003 11:01 PM Craig R. McClanahan wrote:
Adam Hardy wrote:
LookupDispatchAction is great for sorting out the appropriate action
according to which submit button was clicked, even if those submit
buttons have got localized text. But surely it's just pandering to the
poor design of HTML
I am just wondering if anyone has already made a nicer way to manage the
hashmap for the button labels on the LookupDispatchAction?
I hate having to continually add elements in the code when I add a new
button.
---
Thanks
Mick Knutson
coming soon:
Your SOS: Your personal emergency contact system
Message-
From: Mick Knutson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 1:37 PM
To: struts
Subject: externalizing the button hashmap for the LookupDispatchAction?
I am just wondering if anyone has already made a nicer way to manage the
hashmap for the button labels
PROTECTED]
To: 'Struts Users Mailing List' [EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 12:41 PM
Subject: RE: externalizing the button hashmap for the LookupDispatchAction?
I've done it with a LookupMethods.properties file that contains the
following:
button.add=add
button.cancel
: Matt Raible [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 3:42 PM
To: 'Struts Users Mailing List'
Subject: RE: externalizing the button hashmap for the LookupDispatchAction ?
I've done it with a LookupMethods.properties file that contains the
following:
button.add=add
html:submit property=actionType
bean:message key=button.update/
/html:submit
With the help of this I use the LookupDispatchAction which my Action
class extends. This works fine for my submit buttons.
My action-mapping
action path=/MyAction
type=com.mycompany.MyAction
LookupDispatchAction--
Added the following methods
protected Map getKeyMethodMap() {
System.out.println(\n\nHello getKeyMethodMap\n\n);
Map map = new HashMap();
map.put(button.Store, Store);
map.put(button.Delete, Delete);
return map;
}
public ActionForward Store(ActionMapping mapping
LookupDispatchAction--
Added the following methods
protected Map getKeyMethodMap() {
System.out.println(\n\nHello getKeyMethodMap\n\n);
Map map = new HashMap();
map.put(button.Store, Store);
map.put(button.Delete, Delete);
return map;
}
public ActionForward Store
LookupDispatchAction--
Added the following methods
protected Map getKeyMethodMap() {
System.out.println(\n\nHello getKeyMethodMap\n\n);
Map map = new HashMap();
map.put(button.Store, Store);
map.put(button.Delete, Delete);
return map;
}
public ActionForward Store
html:submit property=actionType
bean:message key=button.update/
/html:submit
With the help of this I use the LookupDispatchAction which my Action
class extends. This works fine for my submit buttons.
My action-mapping
action path=/MyAction
type=com.mycompany.MyAction
/
/html:submit
With the help of this I use the LookupDispatchAction which my Action
class extends. This works fine for my submit buttons.
My action-mapping
action path=/MyAction
type=com.mycompany.MyAction
name=myBean
parameter=actionType
Maurice Wijtten wrote:
I have a multilangual form handled by a LookupDispatchAction. When we
recently
added a spanish language, our action throwed an exception because it
could not find
the corresponding key of the submit button. It seemed that a non asci
character was
handled as UTF8
I'm using lookup LookupDispatchAction and to ease development, I've
defined each of my CRUD methods as a global-forward. For example:
forward name=editProfile path=/editUser.do?action=Edit/
However, the problem is that this doesn't work with i18n. What I'd like
to do is to have it dynamically
Colm wrote:
I am getting the following error on , which I can't figure out:
HTTP ERROR: 500 Request[/test] does not contain handler parameter named
updateMethod RequestURI=/clientdb/test.do
If you're getting to that Action with a link, the link should include:
?updateMethod=something at the
: LookupDispatchAction error
Sorry, solution #1 should read:
html:link action=/test.do ... ... /html:link
Not sure if you need the .do part but I do and that can be bad if you change
the extension later. So if you can do it with just action=/test then I
suggest to do it. I will look at mine now to see
Nalini wrote:
Alongside the 'school address' field I have a submit button, 'Find School'
that allows a user to enter part of the
school name or address and hit this 'FindSchool' button which then goes
off to another page (selectSchool.jsp)
that displays a list of matching schools. The user
- Original Message -
From: Wendy Smoak [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Monday, August 11, 2003 10:49 AM
Subject: RE: LookupDispatchAction
Nalini wrote:
Alongside the 'school address' field I have a submit button, 'Find
School'
that allows
]
Subject: LookupDispatchAction error
I am getting the following error on , which I can't figure out:
HTTP ERROR: 500 Request[/test] does not contain handler parameter named
updateMethod
RequestURI=/clientdb/test.do
I am following a couple of decent examples using the LookupDispatchAction
class (pages
it.
-Original Message-
From: Bailey, Shane C. [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2003 12:01 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction error
I think you could do it a couple different ways...
1.
JSP:
bean:define id=lookupName value
The LookupDispatchAction allows you to specify several JSP pages or buttons
on
one page to use single action mapping to achieve CRUD operations. An example
of such action mapping would look like the following:
action
path=/FooCRUDOperation
type=com.myco.editors.FooAction
name=FooForm
scope
a list of matching schools. The user then clicks on their
chosen
school on selectSchool.jsp and is then returned to the RegisterForm with
the
'school name' and 'school address' fields populated.
I have been advised to use a LookupDispatchAction, as a JSP alternative
to
Javascript
'
and 'school address' fields populated.
I have been advised to use a LookupDispatchAction,
as a JSP alternative to Javascript. Has anyone used
it and/ or have an example illustrating its use?
Many Thanks
Nalini
__
Do you Yahoo!?
Yahoo
/td
/tr
/table
/html:form
The Action
public class AddLookupAction extends LookupDispatchAction {
/**
* Constructor for AddLookupAction.
*/
public AddLookupAction() {
super();
}
protected Map getKeyMethodMap() {
Map map = new HashMap
on their chosen school on selectSchool.jsp and
is then returned to the RegisterForm with the 'school name' and 'school address'
fields populated.
I have been advised to use a LookupDispatchAction, as a JSP alternative to Javascript.
Has anyone used it and/ or have an example illustrating its use?
Many
Has anyone got a working example of this so I can see the code and follow it through?
if so, would anyone be willing to post it to me direcly?
I have tried to locate resources online that take you through a worked example without
any luck.
thanks in advance
yan
KickStartESolutions -
PROTECTED]
Sent: Monday, August 11, 2003 7:45 PM
To: [EMAIL PROTECTED]
Subject: LookupDispatchAction
Not sure how best to set this up and indeed, if it is possible so any advice
would be appreciated.
I have a an ActionForm called RegisterForm where a new user to enter their
details (name, email
List'
Subject:RE: LookupDispatchAction error
Yes, you can do it without the .do and it is safer to do so.
You can even do this which is nice:
html:link action=/test?updateMethod=nameOfYourDispatchLookup
...
/html:link
Note the /test? instead of /test.do?
I remember looking at the source
I am getting the following error on , which I can't figure out:
HTTP ERROR: 500 Request[/test] does not contain handler parameter named updateMethod
RequestURI=/clientdb/test.do
I am following a couple of decent examples using the LookupDispatchAction class (pages
128 -130 in Programming
of the paramName
attribute is also suspect, do you have a String in
visible scope named message containing the value to
associate with the parameter id?
m
--- David Jiao [EMAIL PROTECTED] wrote:
Hello,
I have used the LookupDispatchAction with some
buttons and it works
quite well. Now I want to submit
PROTECTED] wrote:
Hello,
I have used the LookupDispatchAction with some
buttons and it works
quite well. Now I want to submit the form by
clicking on a link instead
of a button. I've tried something like this in my
jsp file but it
returns me the error
bean:define id=message
We've done this using the following, non-html:link solution:
script language=JavaScript
!--
function submitPageX(name)
{
document.forms[0].actionX.value=name;
document.forms[0].submit();
}
//--
/script
html:hidden property=actionX value=na /
forward name=NextPage path=/fes/jsp/FESSupportOrgTable.jsp/
/action
against these tags in my jsp:
html:submit property=method value=Query
bean:message key=button.selectOrgs
/html:submit
This is my first crack at subclassing the LookupDispatchAction. Any
ideas as to what I am doing
at subclassing the LookupDispatchAction. Any
ideas as to what I am doing wrong are greatly appreciated. Thanks.
Are you sure you are passing in the form variable called method ?
Make sure on the form that submits you have at the least a hidden
variable called method ie..
html:hidden property
and then in your class that extends LookupDispatchAction extended class,
you need to implement
the
protected Map getKeyMethodMap() {
Map map = new HashMap();
map.put(some.key.value, doit);
return map;
}
public ActionForward doit(ActionMapping mapping,
ActionForm form
path=/pages/choosemonitor.jsp/
forward name=add path=/pages/choosemonitor.jsp/
forward name=checkout path=/pages/contactinfo.jsp/
/action
ACTION:
public class StoreProductDispatchAction extends LookupDispatchAction {
protected Map getKeyMethodMap
On Wed, Jul 23,'03 (04:03 PM GMT-0400), [EMAIL PROTECTED]
wrote:
I am not super-experienced in this, but it seems to me, that your
line:
html:submit property=method value=Query
Oh sorry, I missed that... I doubt the above would ever work. The
method had to match an actual method
On Wed, Jul 23,'03 (04:19 PM GMT-0400), Suzette wrote:
With LookupDispatch you don't have to use a hidden tag. I think the
problem might be in your action itself.
Yea, I'll shut up now:) I forgot also Tim mentioned he wanted to use
LookupDispatchAction. I'm giving messed up advice answering
(ApplicationFilt
erChain.java:193)...blah...blah
-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 4:19 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
With LookupDispatch you don't have to use a hidden tag. I
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
Thanks to all earnest responses. I still have a problem, but it has evolved
a little. I have simplified the syntax (using husted tip 003), so that my
jsp has:
html:submit
bean:message key=button.selectOrgs/
/html:submit
Users Mailing List' [EMAIL PROTECTED]
cc:
Subject:RE: LookupDispatchAction problem
Thanks to all earnest responses. I still have a problem, but it has
evolved a little. I have simplified the syntax (using husted tip 003),
so that my jsp has:
html:submit
bean:message key
04:43 PM
Please respond to Struts Users Mailing List
To: 'Struts Users Mailing List' [EMAIL PROTECTED]
cc:
Subject:RE: LookupDispatchAction problem
I received the same error, so I switched to using my own property method
and if fixed that error.
JSP
.). thanks. Sorry for this going
on-and-on. Who knew...
-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 4:43 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
I received the same error, so I switched
]
Sent: Wednesday, July 23, 2003 5:00 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
Thanks, but I switch it to method, and same error occurs.
Again, I wonder if my problem is related to my resource bundle, not being
able to find it, etc. How can I simply diagnose
Thanks for all help. It is fixed now. God bless you, one and all.
-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:01 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
No prob, here you go
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
Thanks for all help. It is fixed now. God bless you, one and all.
-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:01 PM
To: 'Struts Users Mailing List
Message-
From: Tim Clotworthy
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:07 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
Thanks for all help. It is fixed now. God bless
you, one and all.
-Original Message-
From
, July 23, 2003 5:53 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: LookupDispatchAction problem
Great question. You don't, which is why I did my own
dispatch Action which works off the existence of a
parameters in the request, not their value. In other
words, I made a different
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
Thanks for all help. It is fixed now. God bless you, one and all.
-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:01 PM
To: 'Struts Users Mailing List'
Subject: RE
Thanks.
-Original Message-
From: Suzette Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 6:07 PM
To: 'Struts Users Mailing List'
Subject: RE: LookupDispatchAction problem
You could try using an image button:
html:image property=method pageKey=image.submit
Ok. Thanks.
-Original Message-
From: Michael Ruppin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 5:53 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: LookupDispatchAction problem
Great question. You don't, which is why I did my own
dispatch Action
thanks
-Original Message-
From: Jason Lea [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 6:14 PM
To: Struts Users Mailing List
Subject: Re: LookupDispatchAction problem
Tim Clotworthy wrote:
This is really a simple aside, but is there a way to have the text
(label
named
action
I have tried to use paramId-parameter to attach request parameter to the
link-element,
but I haven't figured out how to do it correctly.
Is it possible to use LookupDispatchAction to dispatsh actions from links at
all?
If not, what would be proper way to implement similar
paramId-parameter to attach request parameter to the
link-element,
but I haven't figured out how to do it correctly.
Is it possible to use LookupDispatchAction to dispatsh actions from links
at
all?
If not, what would be proper way to implement similar functionality?
Should I discard whole
i had posted a question i think 3 days ago about submitting a form to a
LookupDispatchAction without hitting any button and still having a default
value of the parameter handler. someone advised me (im sorry i forgot your
name) that i should have a hidden property of my parameter name, so
Frances Aleah Z. de Guzman wrote:
i had posted a question i think 3 days ago about submitting a form to a
LookupDispatchAction without hitting any button and still having a default
value of the parameter handler. someone advised me (im sorry i forgot your
name) that i should have a hidden
im sorry but im having the same exception
On Thursday 26 June 2003 05:01 pm, Jason Lea wrote:
Frances Aleah Z. de Guzman wrote:
i had posted a question i think 3 days ago about submitting a form to a
LookupDispatchAction without hitting any button and still having a
default value
things I might be able to help better...
--jason
On Thursday 26 June 2003 05:01 pm, Jason Lea wrote:
Frances Aleah Z. de Guzman wrote:
i had posted a question i think 3 days ago about submitting a form to a
LookupDispatchAction without hitting any button and still having a
default value
to help better...
--jason
On Thursday 26 June 2003 05:01 pm, Jason Lea wrote:
Frances Aleah Z. de Guzman wrote:
i had posted a question i think 3 days ago about submitting a form to a
LookupDispatchAction without hitting any button and still having a
default value of the parameter handler
1 - 100 of 279 matches
Mail list logo
