Return-Path: 
 <issues-return-22844-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
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 C2E39D890
	for <apmail-cxf-issues-archive@www.apache.org>;
 Fri,  2 Nov 2012 13:09:15 +0000 (UTC)
Received: (qmail 82414 invoked by uid 500); 2 Nov 2012 13:09:15 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 82276 invoked by uid 500); 2 Nov 2012 13:09:14 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 82245 invoked by uid 99); 2 Nov 2012 13:09:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 13:09:13 +0000
Date: Fri, 2 Nov 2012 13:09:13 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <2108158232.60276.1351861753297.JavaMail.jiratomcat@arcas>
In-Reply-To: <1788900159.56926.1351791192557.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CXF-4608) DOMSource is returned rather than
 StAXSource
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-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489407#comment-13489407 ] 

Daniel Kulp commented on CXF-4608:
----------------------------------


It kind of depends on what you need from the WSDL.   If you just need the SOAPAction, then the action fix is definitely usable.   If you need more than that (primarily would be things like WS-Security Policy fragments or similar), then a deeper workaround would be needed.
                
> DOMSource is returned rather than StAXSource
> --------------------------------------------
>
>                 Key: CXF-4608
>                 URL: https://issues.apache.org/jira/browse/CXF-4608
>             Project: CXF
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 2.4.2
>            Reporter: Steven Hawkins
>            Assignee: Daniel Kulp
>             Fix For: 2.5.7, 2.6.4, 2.7.1
>
>
> A Service created from a WSDL that has doc literal wrapped operations will always return DOMSource regardless of the source type requested by the Dispatch.invoke method.
> For example using a WSDL such as: http://www.xignite.com/xQuotes.asmx?WSDL, the following code highlights the issue with a class cast exception on the last line:
> {code}
> Service service = Service.create(wsdl, new QName("http://www.xignite.com/services/", "XigniteQuotes"));
> Dispatch<T> dispatch = wsdlService.createDispatch(new QName("http://www.xignite.com/services/", "XigniteQuotesSoap"), StAXSource.class, Service.Mode.PAYLOAD);
> QName opQName = new QName("http://www.xignite.com/services/", "GetFundQuote");
> dispatch.getRequestContext().put(MessageContext.WSDL_OPERATION, opQName); 
> StAXSource result = dispatch.invoke(someDoc);
> {code}

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