Timeline for How to isolate a massive and changeable web service [duplicate]
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2014 at 21:24 | history | closed | gnat CommunityBot Bart van Ingen Schenau psr | Duplicate of What is an Anti-Corruption layer, and how is it used? | |
| Jan 13, 2014 at 16:38 | review | Close votes | |||
| Jan 22, 2014 at 21:24 | |||||
| Jan 13, 2014 at 16:18 | comment | added | RobD | Thanks gnat, that's exactly what I had in mind, although much better solved by the Anti-Corruption Layer pattern, unfortunately doesn't get away from having to code all the entities by hand... That being said, posting this question has forced me to come to terms with the inherent problem with the service generated classes; and forced me to come to terms with the fact that there is no other way than to hand-code the mirror classes. I'll have to take the maintenance hit, as distributing the dependency on the web service classes throughout the solution is not an option. | |
| Jan 13, 2014 at 14:47 | review | First posts | |||
| Jan 13, 2014 at 14:50 | |||||
| Jan 13, 2014 at 14:37 | comment | added | gnat | consider establishing Anti-Corruption layer to protect your code from monster and using XSLT to additionally isolate changes in their data format | |
| Jan 13, 2014 at 14:30 | history | asked | RobD | CC BY-SA 3.0 |