struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Krah (JIRA)" <>
Subject [jira] Commented: (WW-2523) NPE in dispatcher cleanup when FilterDispatcher is used in a portlet
Date Tue, 14 Oct 2008 16:40:38 GMT


Torsten Krah commented on WW-2523:

Could this be raised to blocker priority please?
Fixing this in future versions is really a no go because portlet spec v 1.0 (struts
implements) does require to use servlets to deliver resources like images, css or other resource
You can use FilterDispatcher and Jsr168Dispatcher and its working - but only until you want
to stop - restart or redeploy your webapp - the container get stuck because the app cannot
be undeployed.
This is more than a major problem because the complete container (and in a portlet environment
there you got many other apps than your own providing portlets) needs to be killed and "restarted".

> NPE in dispatcher cleanup when FilterDispatcher is used in a portlet
> --------------------------------------------------------------------
>                 Key: WW-2523
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Dispatch Filter, Plugin - Portlet
>    Affects Versions: 2.0.11, 2.1.0
>         Environment: JBoss Portal 2.6.4, Struts 2.1.1
>            Reporter: Nils-Helge Garli
>             Fix For: Future
> When the FilterDispatcher is configured in web.xml, it does cleanup first, then JSR168Dispatcher
does cleanup, and for some reason, the ThreadLocal variable (the actual ThreadLocal variable,
not the value it contain) is null. I don't know if this is an issue only in JBoss.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message