You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Shepherd, Darren S " <da...@citi.com> on 2007/09/14 20:14:48 UTC
Whats the harm in creating a Servlet Dispatcher?
All,
This is regarding Struts 2.0.
I've just ran into what I believe is a bug in WebSphere 6.0 and 6.1 where the filter chain does not get hit on certain RequestDispatcher includes. So I have two options here:
1. Get IBM to fix the bug
2. Rewrite the Filter Dispatcher as a Servlet
My experience is that if I engage IBM my bug will be fixed some time in 2008 (seriously). I'm supposed to be in production before that. So let me know if this is a terrible idea. I'm going to take the filter dispatcher and turn it into a servlet. We do not serve static files from struts. If we do wish to server static files, I will write a filter specifically for that.
Darren
Re: Whats the harm in creating a Servlet Dispatcher?
Posted by cilquirm <aa...@gmail.com>.
I'm pretty sure that making FilterDispatcher a Filter was a design decision
so converting it to a servletdispatcher may not be as easy or as
straightforward as one might think.
If memory serves ( and these days, that's not guaranteed ), it actually used
to be a filter/servlet combination before it got rolled up in to a filter.
For example, it wraps the servletrequest so that the EL can have access to
the value stack. Also, it allows for the static dispatch of the templating
themes.
Coder emptor, is all.
hth + gl,
-a
Shepherd, Darren S -2 wrote:
>
> All,
>
>
>
> This is regarding Struts 2.0.
>
>
>
> I've just ran into what I believe is a bug in WebSphere 6.0 and 6.1 where
> the filter chain does not get hit on certain RequestDispatcher includes.
> So I have two options here:
>
>
>
> 1. Get IBM to fix the bug
> 2. Rewrite the Filter Dispatcher as a Servlet
>
>
>
> My experience is that if I engage IBM my bug will be fixed some time in
> 2008 (seriously). I'm supposed to be in production before that. So let
> me know if this is a terrible idea. I'm going to take the filter
> dispatcher and turn it into a servlet. We do not serve static files from
> struts. If we do wish to server static files, I will write a filter
> specifically for that.
>
>
>
> Darren
>
>
>
--
View this message in context: http://www.nabble.com/Whats-the-harm-in-creating-a-Servlet-Dispatcher--tf4444401.html#a12737527
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Whats the harm in creating a Servlet Dispatcher?
Posted by j alex <st...@gmail.com>.
Can you please explain a bit more on this issue ? - i'm also using WAS
6.1and fear i might run into this down the line. We'll need to use
jsp:forward/include etc. a lot in our app.
-Joseph
On 9/17/07, Paul Benedict <pb...@apache.org> wrote:
>
> Shepherd,
>
> As you know, you can configure a filter for the type of dispatching. Types
> are INCLUDE, FORWARD, ERROR, and * (star). Maybe you should list those
> out.
>
> Also if you create a servlet, can you submit it as a JIRA patch?
>
> Paul
>
> On 9/14/07, Shepherd, Darren S <da...@citi.com> wrote:
> >
> > All,
> >
> >
> >
> > This is regarding Struts 2.0.
> >
> >
> >
> > I've just ran into what I believe is a bug in WebSphere 6.0 and 6.1where
> > the filter chain does not get hit on certain RequestDispatcher
> includes. So
> > I have two options here:
> >
> >
> >
> > 1. Get IBM to fix the bug
> > 2. Rewrite the Filter Dispatcher as a Servlet
> >
> >
> >
> > My experience is that if I engage IBM my bug will be fixed some time in
> > 2008 (seriously). I'm supposed to be in production before that. So let
> me
> > know if this is a terrible idea. I'm going to take the filter
> dispatcher
> > and turn it into a servlet. We do not serve static files from
> struts. If
> > we do wish to server static files, I will write a filter specifically
> for
> > that.
> >
> >
> >
> > Darren
> >
> >
>
iterator with only an int as input value
Posted by Vo Van Thuong <vo...@hn.vnn.vn>.
Hi,
i'm wondering if there is anyway to use <s:iterator> like this:
<s:iterator value="{1..pagesNum}" >
<s:property value="top"/>
</s:iterator>
should be the same as below, if pagesNum=5:
<s:iterator value="{1,2,3,4,5}" >
<s:property value="top"/>
</s:iterator>
Thanks,
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Whats the harm in creating a Servlet Dispatcher?
Posted by Paul Benedict <pb...@apache.org>.
Shepherd,
As you know, you can configure a filter for the type of dispatching. Types
are INCLUDE, FORWARD, ERROR, and * (star). Maybe you should list those out.
Also if you create a servlet, can you submit it as a JIRA patch?
Paul
On 9/14/07, Shepherd, Darren S <da...@citi.com> wrote:
>
> All,
>
>
>
> This is regarding Struts 2.0.
>
>
>
> I've just ran into what I believe is a bug in WebSphere 6.0 and 6.1 where
> the filter chain does not get hit on certain RequestDispatcher includes. So
> I have two options here:
>
>
>
> 1. Get IBM to fix the bug
> 2. Rewrite the Filter Dispatcher as a Servlet
>
>
>
> My experience is that if I engage IBM my bug will be fixed some time in
> 2008 (seriously). I'm supposed to be in production before that. So let me
> know if this is a terrible idea. I'm going to take the filter dispatcher
> and turn it into a servlet. We do not serve static files from struts. If
> we do wish to server static files, I will write a filter specifically for
> that.
>
>
>
> Darren
>
>