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 6D87818D17 for ; Fri, 19 Feb 2016 14:14:18 +0000 (UTC) Received: (qmail 72318 invoked by uid 500); 19 Feb 2016 14:14:18 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 72286 invoked by uid 500); 19 Feb 2016 14:14:18 -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 72270 invoked by uid 99); 19 Feb 2016 14:14:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2016 14:14:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1A8102C14F3 for ; Fri, 19 Feb 2016 14:14:18 +0000 (UTC) Date: Fri, 19 Feb 2016 14:14:18 +0000 (UTC) From: "Julian Peters (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CXF-6791) Nested Abstract classes are not converted correctly from a WSDL 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-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Peters updated CXF-6791: ------------------------------- Attachment: MWE.zip Minimum working example > Nested Abstract classes are not converted correctly from a WSDL > --------------------------------------------------------------- > > Key: CXF-6791 > URL: https://issues.apache.org/jira/browse/CXF-6791 > Project: CXF > Issue Type: Bug > Affects Versions: 3.1.5 > Environment: MacOS 10.11.3, Apache CXF 3.1.5, SoapUI 5.2.1, Oxygen 17.1 > Reporter: Julian Peters > Attachments: MWE.zip > > > The attached example features a message and wrapped header. Both are defined in "abstract.xsd" (with appropriate namespace). In "concrete.xsd" both two new types are defined, both deriving from their respective partners in "abstract". The concrete:message is now wrapping a concrete:header. In the "service.wsdl" i define a service, using the concrete:message in a wrapper element. > Now I use "wsdl2java" for convertion, add a dash of spring-boot to get the whole thing running. The end-result is that for a message like > > > > > >
> fdsafdsafdsafdsa >
>
>
>
>
> i run into an unmarshalling-exception (also attached). The Server apparently tries to instantiate the abstract class (from "abstract.xsd"), not the one from concrete.xsd. I double checked with SoapUI and Oxygen, both seem to have no problem with the wsdl. > Of course, removing the "abstract" from the abstract-Header solves the problem, but that is not really a solution for a contract-first driven project. > (In lack of a better way to submit my files, here's a link: http://www.filedropper.com/mwe > I hope this is an appropriate way to submit files.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)