Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Wed, 15 May 2013 14:59:16 +0000 (UTC)
From: "Isart (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12647758.1368629849143.324037.1368629956509@arcas>
In-Reply-To: <JIRA.12647758.1368629849143@arcas>
References: <JIRA.12647758.1368629849143@arcas>
Subject: [jira] [Created] (DOSGI-183) Link filter chain to CXF webservice
 request processing with DOSGi
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Isart created DOSGI-183:
---------------------------

             Summary: 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