Originally posted by fullyautomatix
View Post
If the schema designer has not thought about how schema entities map to type relationships in the code bindings, you can end up with lots of duplicated code that you can't "common up", because of a lack of common base classes in the bindings. You can get around that using reflection. I removed 75% of a code base recently by doing this. You present a type safe layer to callers, all the reflection is hidden from client code.
I keep coming across this problem. These TIBCO experts write these schema and often they are rubbish.
Leave a comment: