Agreed, Jake. I've never been able to sell a business owner on the complexity of SOAP+WSDLs till we start talking complex return types. Then the light goes on and they start getting it and the efficiency factor really cranks up.
We lack an official architecture at my current assignment, so for complex data types, we had to roll our own xml schema and just keep working closely with our counterparts on the other system till we had all the messages going back and forth smoothly. In that case, the heavy-handed enterprise approach *with* automated code and WSDL generation would have been much nicer.
Unfortunately, this bright spot in the narrative is often too dim to illuminate a lot of IT managers who themselves may be old school developers who look at anything beyond COBOL as just overly complex bells and whistles.
Agreed, Jake. I've never been able to sell a business owner on the complexity of SOAP+WSDLs till we start talking complex return types. Then the light goes on and they start getting it and the efficiency factor really cranks up.
We lack an official architecture at my current assignment, so for complex data types, we had to roll our own xml schema and just keep working closely with our counterparts on the other system till we had all the messages going back and forth smoothly. In that case, the heavy-handed enterprise approach *with* automated code and WSDL generation would have been much nicer.
Unfortunately, this bright spot in the narrative is often too dim to illuminate a lot of IT managers who themselves may be old school developers who look at anything beyond COBOL as just overly complex bells and whistles.