1

I posted another question about same thing with different approach: extending type.

My problem is basically that I made stupid choice with type naming in XSD and question is what happens if I change a type name in schema? The XML my new client would send to old customer created Web Service would be identical, but can it still cause problems?

Community
  • 1
  • 1
char m
  • 7,840
  • 14
  • 68
  • 117

1 Answers1

1

Yes, renaming an XSD type is backward compatible1. All of the same XML documents that were valid before the renaming will be valid after the renaming. In fact, it's better than backward compatible because exactly the same set of XML documents that were valid before the change will be valid after the change.

1Assuming that clients have no direct dependencies against the type names themselves such as via JAXB bindings or xsi:type use in XML doc instances. [Thanks to Petru Gardea.]

Community
  • 1
  • 1
kjhughes
  • 106,133
  • 27
  • 181
  • 240
  • My question title was stupid. As I say in question I knew that XML in messages would be exactly the same so in that sense it's BW-compatible. I was kind of trying to ask is there something more to it. Some validation thing or something i can't think of. – char m Feb 18 '16 at 13:47
  • It's possible that there could be implications if your clients consume your XSD for use in other tools such as JAXB, but that'd be much less important than keeping the changes compatible at the XML/XSD validation level. – kjhughes Feb 18 '16 at 14:04
  • Thanks. I'm in total control of client, but not service. I made the XSD+WSDL, but not the Service. Or Services because already currently there is 2 customer implementations. – char m Feb 19 '16 at 10:15