|
|
|
|
|
|
|
April 2006 - The Tripping Point
-
When I wrote my initial post on my new approach to XSD versioning , I promised that I'd post code. Here's the first cut: class Program { static void OriginalMain( string [] args) { FileStream xml = new FileStream (args[0], FileMode .Open); FileStream...
-
Now matter which way you tackle contract evolution, you need to have a system in place to notify your service consumers. I envision a system based on “service blogs”, or “slogs”. A slog conveys information about the state of a...
-
DJ commented on my post addressing the problem Raimond raised with my versioning strategy . He wondered if he'd missed an earlier post where I argued that you not use XSD to validate your data because if you make content optional, you can't use it to...
-
Craig's last post makes me think we've have come to the same place. The way I see it, people simply can't have everything they want: A flexible system that can evolve A system that's easy to build without knowing anything about the XML layer that we're...
-
Erik commented on my earlier post too. Erik, if I understand you right you want to extend XSD itself. I've done that before without trouble, so I'm wondering what problem you're running into. Can you provide more info?
-
Raimond posted this comment asking a question about my approach to XSD versioning: I see how this model can solve a bunch of the problems, but how to deal with removal of allowed elements? Lets say we have a V1: <Customer> <Name>John Doe<...
-
Craig posted a rebuttal to my earlier post . I maintain that his original advice to implement IXmlSerializable is overkill. His argument is that you're in trouble unless you “explicitly control the order of serialization of [your] web service visible...
-
The single biggest problem in the WS space today is data and service versioning. I've been thinking about this problem for years now, and I finally came to an answer that is simple, straight-forward and plays by all the rules. The inspiration came from...
-
It's almost always Craig who coaxes me back into posting after a long absence. This time, it was this post about the perils of contract first and XmlSerializer. He was talking about the possibility of building types that serializer incorrectly and violate...
-
In case you can't tell, I took the spring off from posting. Now that I have no regular readers (by definition ;-), I figure it's time for me to start posting again. What better place to start than with my change in job. I woke up at the New Year and realized...
|
|
|
|
|
|