Ben,

I understand. For the time being I have simply done what was suggested as not being optimal but is the only work around that I know of which is as follows:

   <filter-mapping>
       <filter-name>StripesFilter</filter-name>
       <url-pattern>/*</url-pattern>
       <dispatcher>REQUEST</dispatcher>
   </filter-mapping>
<filter-mapping>
       <filter-name>DynamicMappingFilter</filter-name>
       <url-pattern>/*</url-pattern>
       <dispatcher>REQUEST</dispatcher>
       <dispatcher>FORWARD</dispatcher>
       <dispatcher>INCLUDE</dispatcher>
   </filter-mapping>

If I understand the issue correctly it appears that the an instance of the StripesFilter servlet needs to be initialized before the DynamicFilterMapping. If that is the case then why doesn't the DynamicMappingFilter extend the StripesFilter vs. not extending it yet depending on it to be initialized before hand but crossing your fingers it gets initialized before hand and is available for use (I realize that it appears that the spec is OK with this and it is more than crossing your fingers but it still seems like a perhaps unnecessary leap of faith)?


I'll also reply to the ticket to point out that I too have experienced the issue on GlassFish v3 Final. When I become more experienced with Stripes I'll look into trying to resolve this as well... .



Ben Gunter wrote:
No, another ticket isn't necessary. It's the same problem on all of the affected containers. I didn't come up with a solution that I liked when I was looking at this a while back, and I haven't had time to look into it in a while.

On Mon, May 10, 2010 at 2:32 AM, Nikolaos Giannopoulos <[email protected] <mailto:[email protected]>> wrote:

    As Nicholas pointed out in a comment on 29/Oct/2009 on this issue:
    http://www.stripesframework.org/jira/browse/STS-678

    "This is happening in GlassFish v3 as well"

    I experienced this same issue just today on GlassFish v3 Final.
     As this is still unresolved and the last update states IBM is
    working on a patch for WAS and the title includes "WAS 6.1" AND
    nobody wants to open tickets that will be closed as duplicates:

    Should I open a ticket specifically for GlassFish v3?

    I also wonder if more than one app server is experiencing this
    issue perhaps a cross container solution should be considered?

    Thoughts?

    --Nikolaos



------------------------------------------------------------------------------

_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to