You could also overwrite addIllegalArgumentException(String fieldName,
IllegalArgumentException e) in your action or one of its superclasses so
that it just logs a warning instead of adding an error.
Geoff
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
hi all,
thanks for the help. my problem stemmed from the misconception that
doexecute would always be called, even if there were errors added. now it
works fine
sincerely
morten wilken
- Original Message -
From: Geoff Carruthers [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March
Jason Carreira wrote:
I started looking at doing this and ran into some snags. For instance,
if the code calling the Proxy wants to get at the Action, how does it do
that? The ActionInvocation won't even have been created yet, if the
Proxy hasn't been executed, and will the Action make sense in a
Here's a suggested solution:
* Each application should have its own xwork.xml file that is placed
at
the root level of the project. For example,
com/indigoegg/myproject/xwork.xml for a project with a root of
com.indigoegg.myproject
* Allow xwork.xml to include other xml files via
hi all,
i have a jsp fragment that i would like to include from two places:
1. from within an iterator (in this case the object that i use is on top of
the stack)
2. from an action directly (in this case the object i use is in a
getobject() method in the action action.
in the first case i can
