Dakota Jack wrote:
My experience is that the computer is always right, so I would look in
my properites file, if I were you, and see whether or not I had
reversed the myButtonForward=go to go=myButtonForward. Did you? I
feel compelled to reiterate that LookupDispatchAction is a fairly poor
exampl
Dakota Jack wrote:
On Tue, 07 Dec 2004 12:02:52 +0100, Alexander Czernay
<[EMAIL PROTECTED]> wrote:
The problem is, that only one of those buttons
works, while the other throws a MissingResourceAction. That sounds like
a typo, but the strange thing is, that it tries to lookup the button&#
Susan Bradeen wrote:
/**
* Key method for mapping methods to buttons
*/
protected Map getKeyMethodMap() {
Map map = new HashMap();
map.put("authors-form.button.create", "create");
map.put("authors-form.button.
I have a strange problem with LookupDispatchAction:
I built a form displaying several entries from a db as a list. There are
several buttons for editing/removing the entries an also two buttons for
paging though the list. The problem is, that only one of those buttons
works, while the other thro
I'm still trying to find a nice way for handling standard
list/create/edit/delete-forms...
After browsing through all the hints and tips I got from here, I started
building an initial form-setup-action using DispatchAction with a
parameter dispatch that should be set to list, create, edit or de
Hollaway, Shedrick L CIV TRIREFFAC wrote:
Alexander,
This should help you understand applying DAO/DTO patterns in a Struts
app: http://javaboutique.internet.com/tutorials/ApacheDAOs/
Shed.
Thanks for all your replys and suggestions, but I'm afraid I didn't ask
the right question. What I really wan
I'm searching for a pattern/best-practise for handling standard
data-manipulation forms (like list, create, edit, update, delete
functionality) in Struts. I've read about the CRUD
(create/read/update/delete) pattern many times, but couldn't find any
in-depth papers on it.
Is there any recommen
The problem is, that the given form actually edits the categories-tree
and as it is presented to the user after editing it, it should be
updated after the form is submitted.
Alexander
Joe Germuska wrote:
Your action isn't executed if validation fails. However, the validation
is performed on a
I have a simple DynaValidatorForm
that is called whtin an action
that inserts so data into the request inside its execute method
public ActionForward execute(
ActionMapping mapping,
ActionForm form,
I'm trying to prepopulate a DynaForm with some values - right now just
hard-coded, later should be taken from a DB. For that I'm using a
SetupAction, that is called to prepopulate the form, insert it into the
request and after that forward to the actual action for presenting the
form to the use
10 matches
Mail list logo
