Chris Nokleberg wrote:
I don't understand this logic. A property default is a default for form
parameters, obviously it can change. If you want to fix the value for a
particular mapping, you add it to actions.xml.
Not quite. In an action there are two sets of parameters:
initialization
Heng Sin Low wrote:
May be don't use reflection then and delegate this to the action itself.
For e.g, this can be implemented by adding an init method to the Action
interface that take a map as parameter. This would also allow us to
differentiate between init parameter ( usually for
On Thu, Jan 02, 2003 at 09:23:19PM +0100, Rickard Öberg wrote:
Chris Nokleberg wrote:
There are some interesting
questions regarding the ordering of all the parameter setting,
though. I'd prefer that the action properties overwrite any form
parameters. If you're using the properties to
, this could help (and be used for the Action field
population, as well)
-Original Message-
From: Patrick Lightbody [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 02, 2003 11:59 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Action configuration XML [Commands]
What
What is missing from this example currently is commands. Any ideas are
welcome here. One option is to have the action declaration look like this:
action name=fooDefault class=SimpleAction.doDefault
interceptors-ref name=default/
result name=success view=bar.action/
/action
i.e.
, but then the burdon is on
the HTML/JSP writers and not the application designer.
-Pat
- Original Message -
From: Rickard Öberg [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 02, 2003 9:41 AM
Subject: Re: [OS-webwork] Action configuration XML [Commands]
Patrick Lightbody
boxed wrote:
I think having an option which will lead to foot-shooting is a bad idea.
And I don't think documentation is a solution for that either.
Correct me if I'm wrong, but didn't pat just suggest that you should be able
to set default parameters on actions in the config file. I don't see
Jason Carreira wrote:
Couldn't the Method objects found the first time through reflection for
parameterizing the Action instances be cached and reused, making the
reflection performance hit negligible? I've never profiled reflection to
see where the biggest performance hit is, but if it's the
On Thu, Jan 02, 2003 at 06:41:59PM +0100, Rickard Öberg wrote:
Patrick Lightbody wrote:
I think that the ability to have parameters applied before the action is
initialized is a feature needed, even if it could be slow. For the most
part
there will be zero params, so the slowdown isn't an
that are
similar (same class) but behave differently based on settings.
-Pat
- Original Message -
From: Rickard Ã-berg [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 02, 2003 10:30 AM
Subject: Re: [OS-webwork] Action configuration XML [Commands]
Patrick Lightbody wrote:
See, I
Patrick Lightbody wrote:
So then how would the situation outlined below work then? I understand the
deployment-settings vs. business login parameter issue, but where would
those kinds of parameters be set? I don't think in the HTML URL would be a
good idea. I like being able to make two different
Bruce Ritchie wrote:
The unfortunate part about using the preferences API is that it ties xw
to jdk 1.4, which will mean that it excludes many many people from using
it (us for example) since many of our customers have and will continue
to run jdk 1.3 for some time. I would prefer an alternate
Rickard Öberg wrote:
I said that you *could* use the Preferences API. If you don't want to,
then don't.
Fair enough. I just wanted to be clear that I don't want it as a dependency :)
Regards,
Bruce Ritchie
smime.p7s
Description: S/MIME Cryptographic Signature
Chris Nokleberg wrote:
Oops: this is to me an obvious case of premature optimization. But
optimization is a maybe not the best word for omitting a feature
completely :-)
Right. The idea was to perhaps find a better way to accomplish the same
thing. Once a good way has been found, then we can
If you read the whole email you'd know why. Let me quote:
But it's a dangerous option, since it may not be apparent that this
slowdown will occur. If possible, configuration of actions should not
occur this way.
Given the huge amount of reflection in webwork anyway, is a little more
going to
May be don't use reflection then and delegate this to the action itself.
For e.g, this can be implemented by adding an init method to the Action
interface that take a map as parameter. This would also allow us to
differentiate between init parameter ( usually for configuration purpose ) and
16 matches
Mail list logo
