cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isart (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DOSGI-183) Link filter chain to CXF webservice request processing with DOSGi
Date Wed, 15 May 2013 16:21:16 GMT

    [ https://issues.apache.org/jira/browse/DOSGI-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658502#comment-13658502
] 

Isart commented on DOSGI-183:
-----------------------------

I've been investigating a little, and it seems to me that any filter chain I hear about assumes
the service is processed within it. May this be part of the servlet API?

Let's consider the following sample:
- A request which body is encoded reaches the servlet container.
- A filter is in place to decode the body and override the request. However, AFAIK, the filter
can not override the request that reached the servlet container. Instead, it overrides only
the request passed to following filters in the filter chain (commonly using an HttpRequestWrapper).
- If service invocation is called out of the filter chain, how can the decoded body reach
the service? Does CXF force to implement an InInterceptor for this matter? 

It looks like filters registered with "org.apache.cxf.httpservice.filter" property don't reach
service invocation. 
Should we assume these filters can not change the request object?


                
> Link filter chain to CXF webservice request processing with DOSGi
> -----------------------------------------------------------------
>
>                 Key: DOSGI-183
>                 URL: https://issues.apache.org/jira/browse/DOSGI-183
>             Project: CXF Distributed OSGi
>          Issue Type: New Feature
>    Affects Versions: 1.4.0
>            Reporter: Isart
>             Fix For: 1.5
>
>
> This issue raises from a conversation in the CXF users mailing list. Please, find first
mail in the thread here:
> https://mail-archives.apache.org/mod_mbox/cxf-users/201305.mbox/%3C51935E08.5040405%40i2cat.net%3E
> As stated there, although there is currently a way to execute a filter  *before* normal
CXF processing takes place, I've been unable to find a way to invoke the normal processing
*within* the filter, as part of the filter chain.
> Some frameworks (i.e. Spring Security) expect service invocation to happen within the
filter chain. And things do not work as expected when that's not the case. (I can not say
whether this is a common behaviour or not, as I'm not very familiar with servlet containers
internals).
> I think having a way for that to happen is a desirable feature.
> It would also solve issue DOSGI-182.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message