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 6D62310045 for ; Fri, 16 Oct 2015 04:23:05 +0000 (UTC) Received: (qmail 94987 invoked by uid 500); 16 Oct 2015 04:23:05 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 94948 invoked by uid 500); 16 Oct 2015 04:23:05 -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 94937 invoked by uid 99); 16 Oct 2015 04:23:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Oct 2015 04:23:05 +0000 Date: Fri, 16 Oct 2015 04:23:05 +0000 (UTC) From: "Chad Wilson (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CXF-6518) Soap envelope namespaces not used during exception detail unmarshalling 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-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960146#comment-14960146 ] Chad Wilson edited comment on CXF-6518 at 10/16/15 4:22 AM: ------------------------------------------------------------ I'm having an almost identical problem with the JAXWS-RI on Java 1.8.0_60 for what it's worth (prefix xsd... same stack trace back up to UnmarshallerImpl); with default JAXB version. Problem doesn't happen on Java 1.7.0_80. I mention this because, with complete naivete, I wonder if a JAXB change has been made that has somehow broken dependencies? was (Author: chadwilson): I'm having an almost identical problem with the JAXWS-RI on Java 1.8.0_60 for what it's worth (prefix xsd... same stack trace back up to UnmarshallerImpl); with default JAXB version. Probably doesn't happen on Java 1.7.0_80. I mention this because, with complete naivete, I wonder if a JAXB change has been made that has somehow broken dependencies? > Soap envelope namespaces not used during exception detail unmarshalling > ----------------------------------------------------------------------- > > Key: CXF-6518 > URL: https://issues.apache.org/jira/browse/CXF-6518 > Project: CXF > Issue Type: Bug > Reporter: Andrew Cleasby > > When handling this SOAP fault response: > ServerFaultCodecom.vmware.pbm.pbmFault.localesummaryInvalid or null error message(vmodl.fault.InvalidArgument) { > faultCause = null, > faultMessage = null, > invalidProperty = resourceType > }resourceType > Fault handling fails due to an unmapped namespace error ("prefix xsd is not bound to a namespace"). It appears that namespace declarations from the SOAP envelope are not propagated when unmarshalling the exception detail in ClientFaultConverter. > The relevant stack trace is: > at com.sun.xml.bind.DatatypeConverterImpl._parseQName(DatatypeConverterImpl.java:369) > at com.sun.xml.bind.v2.runtime.unmarshaller.XsiTypeLoader.parseXsiType(XsiTypeLoader.java:96) > at com.sun.xml.bind.v2.runtime.unmarshaller.XsiTypeLoader.startElement(XsiTypeLoader.java:74) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:576) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:555) > at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(InterningXmlVisitor.java:75) > at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:168) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:244) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:250) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:250) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:281) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:250) > at com.sun.xml.bind.unmarshaller.DOMScanner.scan(DOMScanner.java:127) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:369) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:348) > at org.apache.cxf.jaxb.JAXBEncoderDecoder.doUnmarshal(JAXBEncoderDecoder.java:834) > at org.apache.cxf.jaxb.JAXBEncoderDecoder.access$100(JAXBEncoderDecoder.java:102) > at org.apache.cxf.jaxb.JAXBEncoderDecoder$2.run(JAXBEncoderDecoder.java:894) > at java.security.AccessController.doPrivileged(Native Method) > at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:892) > at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:712) > at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:176) > at org.apache.cxf.interceptor.ClientFaultConverter.processFaultDetail(ClientFaultConverter.java:155) > at org.apache.cxf.interceptor.ClientFaultConverter.handleMessage(ClientFaultConverter.java:82) -- This message was sent by Atlassian JIRA (v6.3.4#6332)