On Thu, Apr 14, 2011 at 3:12 PM, Emi Lu wrote:
> I mean that I agree with Aner. If I just "addActionErrorMessage", but not a
> real ActionError, I would not expect the interceptor stop the workflow :-(
There's no such thing as a "real ActionError". There are error messages.
If there are error mes
Hi Dave,
On Thu, Apr 14, 2011 at 2:43 PM, Emi Lu wrote:
Especially if there were no validation errors,
only error messages added by the application code.
By the way, I agree with this very much!
So you're basically saying that you want to differentiate between two
different types of errors,
On Thu, Apr 14, 2011 at 2:43 PM, Emi Lu wrote:
>> Especially if there were no validation errors,
>> only error messages added by the application code.
> By the way, I agree with this very much!
So you're basically saying that you want to differentiate between two
different types of errors, or at t
On Thu, Apr 14, 2011 at 2:38 PM, Emi Lu wrote:
>> 1. Add an "input" result to your config as previously stated
> Do not know where/what should be set in struts.xml :-(
In the action that causes the 404 because there's no input.
Dave
---
Especially if there were no validation errors,
only error messages added by the application code.
By the way, I agree with this very much!
Emi
- Aner
On 04/14/2011 12:00 PM, Dave Newton wrote:
On Thu, Apr 14, 2011 at 11:54 AM, Aner Perez wrote:
This is an annoying "feature" of the Workflow
Hi Aner,
This is an annoying "feature" of the Workflow interceptor. If
ValidationAware.hasErrors() returns true, the interceptor chain is
stopped and Action.INPUT is returned. If you put error messages on your
action, it will make hasErrors return true which will force the "input"
result to be
Hello,
All right, put "input".
I found this:
http://glindholm.wordpress.com/2008/07/02/preserving-messages-across-a-redirect-in-struts-2/
But no one ever provide an example of where to set input feature.
My situation is:
(part1)
browse_action1
(part2)
On Thu, Apr 14, 2011 at 12:18 PM, Aner Perez wrote:
> It's annoying because it uses a side effect to figure out if validation
> failed.
> Instead of setting some flag when any validation fails and using that flag
> to determine if the INPUT result should be displayed, it is using the number
> of
>I wouldn't consider storing HTML in a properties file. That sounds
messy.
Not only does it sound messy, it looks pretty fugly, too!
> I would explore using Velocity.
Thank you for the guidance, sir!
Sincerely,
Beez
-
To unsu
>Before the email requirement, the information was stored in a jsp and
>included where necessary using tiles. The complexity of compiling a jsp
>and returning the resulting html is simply an inadequate solution.
I would explore using Velocity. Struts will display a Velocity page or you
can shove
It's annoying because it uses a side effect to figure out if
validation failed. Instead of setting some flag when any validation
fails and using that flag to determine if the INPUT result should be
displayed, it is using the number of error messages to determine if
there were any validation er
I have the following business requirement:
-Include "common contact information" (i.e., the director and
her staff) in a view that will also be used at the bottom of an email
sent out by the same system
We would like to keep the formatting of said contact information
consistent wherever it
Hi Ilya,
maybe this will help:
Best greetings,
Paweł Wielgus.
2011/4/11 Ilya Kazakevich :
> Hello,
>
> I store all my jspx templates in /WEB-INF/templates//
> I am tired of copy/paste like
>
> /WEB-INF/templates/foo/success.jspx
> /WEB-INF/templates/foo/foo.jspx
>
> All my templates are in WEB-
On Thu, Apr 14, 2011 at 11:54 AM, Aner Perez wrote:
> This is an annoying "feature" of the Workflow interceptor. If
> ValidationAware.hasErrors() returns
> true, the interceptor chain is stopped and Action.INPUT is returned. If you
> put error messages
> on your action, it will make hasErrors
This is an annoying "feature" of the Workflow interceptor. If
ValidationAware.hasErrors() returns true, the interceptor chain is
stopped and Action.INPUT is returned. If you put error messages on
your action, it will make hasErrors return true which will force the
"input" result to be returne
Did you try adding an "input" result and seeing if the issue went away?
d.
On Thu, Apr 14, 2011 at 10:12 AM, Emi Lu wrote:
>
>> I'm still guessing it's a validation thing--put an "input" result in
>> there and check.
>>
>> Also, by naming the results the same as the actions you're actually
>> ci
I'm still guessing it's a validation thing--put an "input" result in
there and check.
Also, by naming the results the same as the actions you're actually
circumventing one of the reasons for abstracting the result names from
everything else. Even for test apps it's just not a good habit, IMO.
On Thu, Apr 14, 2011 at 6:57 AM, Sunil Choppara wrote:
> Can any one tell me to how we can Highlight Error Fields if we use
> dynaValidator and
> Dispatch action class.
I'm not aware it's any different based on what action class or form
style is being used. So what do you mean by "highlight"? Is
Hi all
Can any one tell me to how we can Highlight Error Fields if we use
dynaValidator and Dispatch action class.
This is very urgent for me; please post your comments quickly.
Regards
Sunil
The information contained in this e-mail message and any attachm
you can put it some where and send we back the link if it will not be
intercepted again !!
2011/4/13 Biesbrock, Kevin
> Ah, good point. So it's probably visible in the source, just not
> interpreted correctly when displaying the email.
>
>
> Beez
>
> -Original Message-
> From: Dave Newto
"
"
--
View this message in context:
http://struts.1045723.n5.nabble.com/form-action-is-not-calling-while-click-on-submit-button-Struts2-0-tp4292686p4302460.html
Sent from the Struts - User mailing list archive at Nabble.com.
21 matches
Mail list logo
