Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CE56491C2 for ; Tue, 27 Nov 2012 09:26:01 +0000 (UTC) Received: (qmail 66391 invoked by uid 500); 27 Nov 2012 09:26:01 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 66324 invoked by uid 500); 27 Nov 2012 09:26:01 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 66285 invoked by uid 99); 27 Nov 2012 09:26:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Nov 2012 09:26:00 +0000 Date: Tue, 27 Nov 2012 09:26:00 +0000 (UTC) From: "Richard Opalka (JIRA)" To: issues@cxf.apache.org Message-ID: <1770236518.26736.1354008360489.JavaMail.jiratomcat@arcas> In-Reply-To: <1083313726.26734.1354008239673.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (CXF-4653) CXF continuations portability issue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Opalka updated CXF-4653: -------------------------------- Attachment: CXF4653.patch Attaching patch proposal > CXF continuations portability issue > ----------------------------------- > > Key: CXF-4653 > URL: https://issues.apache.org/jira/browse/CXF-4653 > Project: CXF > Issue Type: Bug > Components: Transports > Reporter: Richard Opalka > Fix For: 2.7.1 > > Attachments: CXF4653.patch > > > According to our discussion on CXF dev list I verified the Dan's suggestion works on top of JBoss Web. -- 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