Hello Guys,
I was just wondering if any one has come across an issue like
this.
I have an interceptor that redirects a user to a certain page if the user
does not fulfill certain requirements my application needs.
For instance, when a user is logged in(LoginActionBean) to the app, and the
user does not have a security question set, my interceptor redirects the
user to the securityActionBean to get that done. After the user has
fulfilled this requirement, he is suppose to be redirected to the main page
of the app and continue his business. In firefox, this works perfectly. In
IE 6 and 7, it seems like stripes calls the action performed on the
securityActionBean twice. This causes a DB error because the user seems to
be saving unique entries into the DB. To me this seem to be a browser issue.
Something to do with how browsers handle redirects. Or something on the JSP
that seems to be telling stripes to call the actionBean twice. Not sure if
any one has come across this issue.
Thanks,
Osagie Uwaifo
On Thu, Oct 1, 2009 at 6:51 AM, <stripes-users-requ...@lists.sourceforge.net
> wrote:
> Send Stripes-users mailing list submissions to
> stripes-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/stripes-users
> or, via email, send a message with subject or body 'help' to
> stripes-users-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> stripes-users-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Stripes-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Locale Picker and request interceptor
> (Oscar Westra van Holthe - Kind)
> 2. Re: Localization and MessageFormat (Freddy Daoud)
> 3. Missing StripesRequestWrapper when using web.xml to direct
> 404 errors to a Stripes action. (Geoff Shuetrim)
> 4. Re: Missing StripesRequestWrapper when using web.xml to
> direct 404 errors to a Stripes action. (Ben Gunter)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 Sep 2009 20:37:07 +0200
> From: Oscar Westra van Holthe - Kind <kin...@xs4all.nl>
> Subject: Re: [Stripes-users] Locale Picker and request interceptor
> To: Stripes Users List <stripes-users@lists.sourceforge.net>
> Message-ID: <20090930183707.ga2...@odin>
> Content-Type: text/plain; charset=us-ascii
>
> On 24-09-2009 at 16:45, Lionel wrote:
> > Hi all !
> >
> > I would like to set the user locale as a thread local variable from an
> > interceptor (based on the user account) and get this value from a custom
> > LocalePicker.
> > But it seems that the LocalePicker.getLocale() is called before
> > interceptors.
> > Is there some way to configurer the execution order to have muy
> interceptor
> > called before the LocalePicker ?
>
> No. But you can do the following:
> 1. Create a custom ActionBeanContext that retreives the user account
> information based on either request.getUserPrincipal(), other request
> data, or the session. Put your variable in a request attribute.
> Configure the StripesFilter to use this class directly or put it in an
> extension package.
> 2. Create a custom LocalePicker (subclass the DefaultLocalePicker for
> example). It get's the request, so you can access your variable to
> determine the locale to use.
> Configuration is analogous to point 1.
>
>
> Oscar
>
> --
> ,-_
> /() ) Oscar Westra van Holthe - Kind
> http://www.xs4all.nl/~kindop/<http://www.xs4all.nl/%7Ekindop/>
> (__ (
> =/ () DRM "manages access" in the same way that a jail "manages freedom".
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 30 Sep 2009 18:47:44 +0000 (UTC)
> From: Freddy Daoud <xf2...@fastmail.fm>
> Subject: Re: [Stripes-users] Localization and MessageFormat
> To: stripes-users@lists.sourceforge.net
> Message-ID: <loom.20090930t204703-...@post.gmane.org>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Philip,
>
> - Thanks Freddy -
> - So I'm still trying to figure out what all the rules are and when i
> - use: ' vs ''
> -
> - <fmt:message key="foo"/> USE '
> - <fmt:message key="foo"><fmt:param value="bar"></fmt:message> USE ''
> -
> - <stripes:label name="foo"/> -- USE '
> - <stripes:error name="bar"/> -- '' USE ''
> -
> - Is that right? Blurg
>
> Yes that is correct. Indeed, that is somewhat confusing. :/
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 1 Oct 2009 15:08:25 +1000
> From: Geoff Shuetrim <ge...@galexy.net>
> Subject: [Stripes-users] Missing StripesRequestWrapper when using
> web.xml to direct 404 errors to a Stripes action.
> To: stripes-users@lists.sourceforge.net
> Message-ID:
> <7368e2920909302208u37cb2b0s9564e348c1703...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I am using Stripes 1.5.1 and Tomcat 6.
>
> I am trying to use a stripes action to respond to requests that result in a
> 404 error.
>
> I have added:
>
> <error-page>
> <error-code>404</error-code>
> <location>/errors/Error.action</location>
> </error-page>
>
> to the web application's web.xml file.
>
> When I trigger a 404 error, the following log entry is generated and the
> web
> browser is sent to the default 404 error page.
>
> 01/10/2009 2:53:49 PM org.apache.catalina.core.ApplicationDispatcher invoke
> SEVERE: Servlet.service() for servlet StripesDispatcher threw exception
> java.lang.IllegalStateException: A request made it through to some part of
> Stripes without being wrapped in a StripesRequestWrapper. The StripesFilter
> is responsible for wrapping the request, so it is likely that either the
> StripesFilter is not deployed, or that its mappings do not include the
> DispatcherServlet _and_ *.jsp. Stripes does not require that the Stripes
> wrapper is the only request wrapper, or the outermost; only that it is
> present.
> at
>
> net.sourceforge.stripes.controller.StripesRequestWrapper.findStripesWrapper(StripesRequestWrapper.java:81)
> at
>
> net.sourceforge.stripes.controller.DefaultActionBeanPropertyBinder.bind(DefaultActionBeanPropertyBinder.java:207)
> at
>
> net.sourceforge.stripes.controller.DispatcherHelper$3.intercept(DispatcherHelper.java:194)
> at
>
> net.sourceforge.stripes.controller.ExecutionContext.proceed(ExecutionContext.java:158)
> at
>
> net.sourceforge.stripes.controller.BeforeAfterMethodInterceptor.intercept(BeforeAfterMethodInterceptor.java:113)
> at
>
> net.sourceforge.stripes.controller.ExecutionContext.proceed(ExecutionContext.java:155)
> at
>
> net.sourceforge.stripes.controller.ExecutionContext.wrap(ExecutionContext.java:74)
> at
>
> net.sourceforge.stripes.controller.DispatcherHelper.doBindingAndValidation(DispatcherHelper.java:190)
> at
>
> net.sourceforge.stripes.controller.DispatcherServlet.doBindingAndValidation(DispatcherServlet.java:254)
> at
>
> net.sourceforge.stripes.controller.DispatcherServlet.service(DispatcherServlet.java:148)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> at
>
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:438)
> at
>
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
> at
>
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
> at
>
> org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416)
> at
>
> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343)
> at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
> at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> at
> org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:427)
> at
>
> org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:384)
> at
> org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1527)
> at java.lang.Thread.run(Thread.java:619)
>
> Any ideas on how to make such requests for Stripes actions be wrapped
> properly?
>
> Thanks
>
> Geoff Shuetrim
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Thu, 1 Oct 2009 07:50:35 -0400
> From: Ben Gunter <gunter...@gmail.com>
> Subject: Re: [Stripes-users] Missing StripesRequestWrapper when using
> web.xml to direct 404 errors to a Stripes action.
> To: Stripes Users List <stripes-users@lists.sourceforge.net>
> Message-ID:
> <885e877b0910010450u7f3e75c0yec8325ff088ef...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> You have to add <dispatcher>ERROR</dispatcher> to your StripesFilter
> mapping, similar to how it's shown in the DynamicMappingFilter javadocs.
>
>
> http://stripes.sourceforge.net/docs/current/javadoc/net/sourceforge/stripes/controller/DynamicMappingFilter.html
>
> -Ben
>
> On Thu, Oct 1, 2009 at 1:08 AM, Geoff Shuetrim <ge...@galexy.net> wrote:
>
> > I am using Stripes 1.5.1 and Tomcat 6.
> >
> > I am trying to use a stripes action to respond to requests that result in
> a
> > 404 error.
> >
> > I have added:
> >
> > <error-page>
> > <error-code>404</error-code>
> > <location>/errors/Error.action</location>
> > </error-page>
> >
> > to the web application's web.xml file.
> >
> > When I trigger a 404 error, the following log entry is generated and the
> > web browser is sent to the default 404 error page.
> >
> > 01/10/2009 2:53:49 PM org.apache.catalina.core.ApplicationDispatcher
> invoke
> > SEVERE: Servlet.service() for servlet StripesDispatcher threw exception
> > java.lang.IllegalStateException: A request made it through to some part
> of
> > Stripes without being wrapped in a StripesRequestWrapper. The
> StripesFilter
> > is responsible for wrapping the request, so it is likely that either the
> > StripesFilter is not deployed, or that its mappings do not include the
> > DispatcherServlet _and_ *.jsp. Stripes does not require that the Stripes
> > wrapper is the only request wrapper, or the outermost; only that it is
> > present.
> > at
> >
> net.sourceforge.stripes.controller.StripesRequestWrapper.findStripesWrapper(StripesRequestWrapper.java:81)
> > at
> >
> net.sourceforge.stripes.controller.DefaultActionBeanPropertyBinder.bind(DefaultActionBeanPropertyBinder.java:207)
> > at
> >
> net.sourceforge.stripes.controller.DispatcherHelper$3.intercept(DispatcherHelper.java:194)
> > at
> >
> net.sourceforge.stripes.controller.ExecutionContext.proceed(ExecutionContext.java:158)
> > at
> >
> net.sourceforge.stripes.controller.BeforeAfterMethodInterceptor.intercept(BeforeAfterMethodInterceptor.java:113)
> > at
> >
> net.sourceforge.stripes.controller.ExecutionContext.proceed(ExecutionContext.java:155)
> > at
> >
> net.sourceforge.stripes.controller.ExecutionContext.wrap(ExecutionContext.java:74)
> > at
> >
> net.sourceforge.stripes.controller.DispatcherHelper.doBindingAndValidation(DispatcherHelper.java:190)
> > at
> >
> net.sourceforge.stripes.controller.DispatcherServlet.doBindingAndValidation(DispatcherServlet.java:254)
> > at
> >
> net.sourceforge.stripes.controller.DispatcherServlet.service(DispatcherServlet.java:148)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> > at
> >
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> > at
> >
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:438)
> > at
> >
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
> > at
> >
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
> > at
> >
> org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416)
> > at
> >
> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343)
> > at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
> > at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> > at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> > at
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> > at
> > org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:427)
> > at
> >
> org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:384)
> > at
> > org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1527)
> > at java.lang.Thread.run(Thread.java:619)
> >
> > Any ideas on how to make such requests for Stripes actions be wrapped
> > properly?
> >
> > Thanks
> >
> > Geoff Shuetrim
> >
> >
> >
> ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry® Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9-12, 2009. Register
> now!
> > http://p.sf.net/sfu/devconf
> > _______________________________________________
> > Stripes-users mailing list
> > Stripes-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/stripes-users
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
>
> ------------------------------
>
> _______________________________________________
> Stripes-users mailing list
> Stripes-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
> End of Stripes-users Digest, Vol 41, Issue 1
> ********************************************
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
