cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Commented] (CXF-4608) DOMSource is returned rather than StAXSource
Date Fri, 02 Nov 2012 13:09:13 GMT


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:
>             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:, the following
code highlights the issue with a class cast exception on the last line:
> {code}
> Service service = Service.create(wsdl, new QName("",
> Dispatch<T> dispatch = wsdlService.createDispatch(new QName("",
"XigniteQuotesSoap"), StAXSource.class, Service.Mode.PAYLOAD);
> QName opQName = new QName("", "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:

View raw message