cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikhail GRUSHINSKIY <>
Subject CXF Aegis binding and namespace inheritance
Date Tue, 11 Jun 2013 18:59:11 GMT
Hello CXF Devs,

After upgrade of CXF from 2.2.7 to 2.7.4 we started getting different namespace for an element
in XML SOAP messages

2.2.7 -->
<ns2:status xmlns:ns2="">
                               <ns3:code xmlns:ns3="">A</ns3:code>
                               <ns3:description xmlns:ns3="">Active</ns3:description>
2.7.4 -->
 <ns2:status xmlns:ns2="">

'status' element namespace changed. 'status' property is defined not in Account class but
in its superclass Party.
So in case of 2.2.7
aegis is taking namespace for 'status' from 'Account'
and in case of 2.7.4 from its superclass 'Party'.

@XmlType(name = "Account", namespace = "",
propOrder = {
public class Account
    extends Party
    implements Serializable

@XmlType(name = "Party", propOrder = {
public class Party
    implements Serializable

    namespace = "",
    xmlns = {
            prefix = "xsi",

How can we change XML serialization to be backward compatible? (I.e. make aegis 2.7.4 generate
same namespaces as in older version)
Is there an option to turn on or any other way?


This message and any attachments (the "message") is intended solely for 
the addressees and is confidential. If you receive this message in error, 
please delete it and immediately notify the sender. Any use not in accord 
with its purpose, any dissemination or disclosure, either whole or partial, 
is prohibited except formal approval. The internet can not guarantee the 
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) 
not therefore be liable for the message if modified. Please note that certain 
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message