It seems that the access is still not filtered for some reason.
If it's filtered, a line like the following is output to the log when an 
error occurs (log level has to be set to DEBUG).

Intercepting request to URL: /CONTEXT/WEB-INF/error.jsp

--
I should have asked this first, but which container and jdk are you using?
I had confirmed it worked with Tomcat 5.5.26 and Jetty 6.1.8 on Java 5.

// Iwao

Matthew Altman wrote on 08.4.8 2:44 PM:
> Bummer, I thought for sure that would have taken care of the issue. But 
> it didn't.
> Still getting:
> Apr 8, 2008 5:35:57 AM org.apache.catalina.core.ApplicationDispatcher invoke
> SEVERE: Servlet.service() for servlet jsp threw exception
> java.lang.NullPointerException
>         at 
> net.sourceforge.stripes.tag.UseActionBeanTag.doStartTag(UseActionBeanTag.java:90)
>         at 
> org.apache.jsp.WEB_002dINF.layout.standard_jsp._jspx_meth_stripes_005fuseActionBean_005f0(standard_jsp.java:195)
>         at 
> org.apache.jsp.WEB_002dINF.layout.standard_jsp._jspx_meth_c_005fif_005f0(standard_jsp.java:168)
>         at 
> org.apache.jsp.WEB_002dINF.layout.standard_jsp._jspx_meth_stripes_005flayout_002ddefinition_005f0(standard_jsp.java:108)
>         at 
> org.apache.jsp.WEB_002dINF.layout.standard_jsp._jspService(standard_jsp.java:82)
>         at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> 
> I looked at UseActionBeanTag.java line 90. And the NPE must be due to 
> the fact that StripesFilter.getConfiguration() is returning null because 
> it then attempts to call getActionResolver() on it.
> But if ERROR's are also now getting filtered through the StripesFilter, 
> why wouldn't a Configuration be created?
> 
> -Matthew
> 
> 
> On Mon, Apr 7, 2008 at 8:20 AM, Matthew Altman <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
> 
>     No, I wasn't aware of it, Iwao.
>     I'll check that out right away.
>     Because what I did previously was create some modified versions of
>     my templates, because I had to remove all of the ActionBean stuff.
>     So I really didn't have the same layout or functionality as my other
>     pages (no login/logout, etc).
>     But if it's as simple as setting the ERROR dispatcher I'll be quite
>     happy.
> 
>     Thanks,
>     -Matthew
> 
> 
> 
>     On Mon, Apr 7, 2008 at 6:35 AM, Iwao AVE! <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
> 
>         Hi Matthew,
> 
>         To apply StripesFilter on error page, you need ERROR dispatcher type
>         defined for the JSP filter mapping in your web.xml.
> 
>         <filter-mapping>
>           <filter-name>StripesFilter</filter-name>
>           <url-pattern>*.jsp</url-pattern>
>           <dispatcher>REQUEST</dispatcher>
>           <dispatcher>ERROR</dispatcher>
>         </filter-mapping>
> 
>         Forgive me if you are already aware of it ;)
> 
>         HTH,
>         Iwao
> 
>         Matthew Altman wrote on 08.4.6 11:43 AM:
>          > Thanks a lot Freddy.
>          > Yeah, I'll try creating another more minimal layout for the
>         error page
>          > and see if that works.
>          >
>          > Has anyone else successfully used layouts and other stripes
>         tags within
>          > error pages? If so, can you post an example?
>          >
>          > Thanks,
>          > -Matthew
>          >
>          >
>          > On Sat, Apr 5, 2008 at 8:23 PM, Freddy D. <[EMAIL PROTECTED]
>         <mailto:[EMAIL PROTECTED]>
>          > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>          >
>          >     Hi Matthew,
>          >
>          >      > I'm using 1.4.3 I was testing all of the pages in the
>         app, and
>          >     everything was
>          >     working just fine. All of the pages use that same layout.
>         Only when I
>          >     intentionally hit a nonexistent page to test the 404 did
>         I get that
>          >     error.
>          >
>          >     It looks like when you are using a URL to test a
>         non-existent page, this
>          >     causes the request _not_ to go through the Stripes
>         Filter. Then, in your
>          >     JSP, you are using the s:useActionBean tag which needs
>         the Stripes
>          >     Filter
>          >     to obtain the configuration. That is why you are seeing
>         the exception,
>          >     "Something is trying to access the current Stripes
>         configuration but the
>          >     current request was never routed through the
>         StripesFilter! As a
>          >     result..."
>          >
>          >     So, you might need to make your error JSP not rely on
>         useActionBean. I'm
>          >     not sure if the Stripes layouts would still work.
>          >
>          >     Depending on what you are doing with useActionBean, you
>         may be able
>          >     to get
>          >     the equivalent working with either jsp:useBean or
>         jsp:include. Let
>          >     me know
>          >     if you need more help on this.
>          >
>          >     Hope this helps to get your error page working.
>          >
>          >     Cheers,
>          >     Freddy

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users

Reply via email to