Hi Dave,
thanks, we already solve the interceptor issue, we need to include the
defaultstack before the custom interceptor..
after that it's working fine...
Regards
Yanto
On Thu, Jun 18, 2009 at 7:36 PM, Dave Newton wrote:
> Yanto wrote:
>
>> thanks, we are able to run the interceptor now, but
Yanto wrote:
thanks, we are able to run the interceptor now, but we have another issue,
the interceptor will Loop,
we create the sample follow the code from the webworks
*public* *class* *InterceptorSample* *extends* AbstractInterceptor {
@Override
*public* String intercept(ActionInv
Hi Wes,
thanks for the explaination, we decide to use the simple theme and use the
tag to display the error.
Case closed, thanks for others also that already help...
Regards
Yanto
On Wed, Jun 17, 2009 at 8:57 PM, Wes Wannemacher wrote:
> All of the themes "work" with validation, it just depends
All of the themes "work" with validation, it just depends on what you
are expecting out of validation. The validation workflow interceptors
will stop processing if validation fails and then indicate to the
framework that the "input" result should be rendered. Whether and how
you show the validation
Finally we found the issue is actually with the theme,
we need to stop using simple themeand the validation and interceptor
will work.
http://www.nabble.com/Struts2-Validation-not-working-with-theme-simple-td23127366.html
just wondering, is there any other theme that working with validation
Hi Volker,
thanks, we are able to run the interceptor now, but we have another issue,
the interceptor will Loop,
we create the sample follow the code from the webworks
*public* *class* *InterceptorSample* *extends* AbstractInterceptor {
@Override
*public* String intercept(ActionIn
Hi Dave,
after following your note, we are able to run our sample interceptor,
however now we have another issue the sample interceptor will always
looping,
since we have the following code in the sample interceptor,
*return* invocation.invoke();
but the sample interceptor will not run, if we ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
sounds like you mixed up interceptors and action classes.
Look at *http://struts.apache.org/2.x/docs/interceptors.html
*regards
Volker
Yanto schrieb:
> Hi,
>
>
> I am trying to use the following simple interceptor test the
> interceptor conce
Yanto wrote:
This will configure *only* the "sample" interceptor.
If you specify *any* interceptors on a per-action basis you must
configure *all* interceptors. This can be done in several ways.
- specify all interceptors in the action's configuration (you can
specify interceptor stac
after we add validationWorkflowStack interceptor before the timer, then the
timer interceptor will show the result,
if we use the above in the action it is printing the timer value like below
[2009-06-16 18:03:41,218] INFO
com.opensymphony.xwork2.interceptor.TimerInterceptor - Executed actio
Hi Pawel,
thanks for the link
we already check the interceptor for the namespace, and it's showing the
interceptor yang we configure in the config-browser-plugin
TimerInterceptor
com.opensymphony.xwork2.interceptor.TimerInterceptor
but, when we check from the Apache console, the interceptor is
Hi Yanto,
use this [1] plugin to verify if all namespaces and stacks are as You
think they should be.
[1] http://struts.apache.org/2.x/docs/config-browser-plugin.html
Best greetings,
Paweł Wielgus.
2009/6/16 Yanto :
> Hi,
>
>
> I am trying to use the following simple interceptor test the interc
Hi,
I am trying to use the following simple interceptor test the interceptor
concepts but is not happened while calling the action class.
Sample interceptor class.
*import* *com.opensymphony.xwork2.ActionContext*;
*import* com.opensymphony.xwork2.ActionInvocation;
*import* com.opensymphon
13 matches
Mail list logo
