Ted,
tnanks for your reply. This action was just an idea from me. I haven't thought
about including it into the struts stuff. Nevertheless I am pleased if it happens
and somebody find it usefull.
Dmitri Valdin
Datum: 24.11.2001 17:32
An:Struts Developers List [EMAIL
be a refactoring and split of the
one I already submitted.
Erik
- Original Message -
From: Dimitri Valdin [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Tuesday, November 20, 2001 5:17 AM
Subject: Antwort: Re: [SUBMIT] LookupDispatchAction - how to handle multiple
I just don't feel that struts-config is the appropriate place to deal with
those kinds of mappings as they are very concrete to the action. A matter
of preference, I suppose.
Is that a fair enough summary?
Sure.
I still like my design better! :) But yours works and certainly is a viable
Erik,
I don't understand what you mean by application properties playing a role.
How so?
buttons.add buttons.delete have to be defined, which is not obvious for somebody
who does not take care about internationalization. In fact I would define the
resources in any case. But what about images
buttons.add buttons.delete have to be defined, which is not obvious for
somebody
who does not take care about internationalization. In fact I would define
the
resources in any case. But what about images ? How do you want to handle
them ?
For images I would put the image name in
Yet another approach would be to use an image tag:
html:image page=/images/lock.gif property=lock /
html:image page=/images/unlock.gif property=unlock /
html:image page=/images/delete.gif property=delete /
and check parameter in action:
if (request.getParameter(lock.x) != null) {
