suppose, i'm not using timer interceptor and suppose i'm using timer
interceptor then in such a case that interceptor only triggered but it's
executing all interceptor in reverse order once again in post processing.
why?
--
View this message in context:
On Mon, Jul 25, 2011 at 9:58 AM, mohan rao [via Struts]
ml-node+4629574-1865382249-219...@n5.nabble.com wrote:
suppose, i'm not using timer interceptor and suppose i'm using timer
interceptor then in such a case that interceptor only triggered but it's
executing all interceptor in reverse
Actually, no, it's not executing them again, it's finishing the original
execution. The interceptor does whatever it's supposed to do before the
execution of the action, it then turns over control to Struts which decides
whether there is another interceptor in the chain, or whether it's time to
Hello,
I always get the following exception, does someone know why?
web.xml
filter
filter-namestruts/filter-name
filter-classorg.apache.struts2.dispatcher.FilterDispatcher/filter-class
init-param
param-nameactionPackages/param-name
Hello,
I tried dispatcher.ng.filter.StrutsPrepareAndExecuteFilter as well, but
still got the following error.
Could someone help?
Thank you,
Emi
filter
filter-namestruts2/filter-name
Hello list! I'm making a research about Struts2 and there are several things
that I don't understand (haha), I have studied really hard and I think I'm
in the righ way now, but there's a thing that i don't understand about this
examples i found about interceptors, i'm talking about the parameter
There are some interceptors, like validator one, which are not triggered in
case of the name of the invoked method matches one of the list element
(there is no reason to validate an input action, you don't yet obtain the
user input, so you have anything to validate).
Hope this help.
Maurizio
Thanks Maurizio, let me see if i got it straight. You mean that, for
example:
interceptor-ref name=validation
param
name=excludeMethodsinput,back,cancel/param/interceptor-ref
won't be executed by results whose name is input, back or cancel?
2011/7/25 Maurizio Cucchiara
Not exactly. It would not execute for actions whose method name is input,
back or cancel. It's on the action side, not the result side.
(*Chris*)
On Mon, Jul 25, 2011 at 2:59 PM, Mano Pájaro mano0...@gmail.com wrote:
Thanks Maurizio, let me see if i got it straight. You mean that, for
I see mm so, it only acts on the action which method attribute is diferent
from in the list, that's it? :D
2011/7/25 Chris Pratt thechrispr...@gmail.com
Not exactly. It would not execute for actions whose method name is input,
back or cancel. It's on the action side, not the result side.
Exactly, so the default (execute) would run the validation, but not the ones
that are listed.
(*Chris*)
On Mon, Jul 25, 2011 at 4:53 PM, Mano Pájaro mano0...@gmail.com wrote:
I see mm so, it only acts on the action which method attribute is diferent
from in the list, that's it? :D
Thank u for everything! I will keep studying! :D
--
Manolo Pájaro Santander
Ingeniero de Sistemas VIII Semestre (Actual)
Promoviendo el Software Libre
CUSOL-UAC
Linux Registered User # 522026
2011/7/25 Emi Lu em...@encs.concordia.ca:
filter-mapping
filter-namestruts/filter-name
url-pattern/*/url-pattern
dispatcherREQUEST/dispatcher
dispatcherINCLUDE/dispatcher
/filter-mapping
Did you try to remove these dispatcher params ? Or add FORWARD ?
Regards
--
13 matches
Mail list logo