Который является лучшим подходом к веб-сервисам - сокращаются сначала или контракт в последний раз?
Вы, вероятно, хотите сделать SELECT?
SELECT replace(barcode, right(barcode,1),'') AS test from outerbarcodes
2 ответа
Contract-first is the generally accepted 'best practice.'
It makes you be very clear with both the producer and consumer of the service exactly what is needed and what is expected. This becomes especially important when you start trying to convert java types -> xml types. You're also able to reuse schemas across different web service.
I suspect the answer is a definite "it depends."
The issue is that if you build and publish your contract, you're bound by it. This makes change harder. not impossible, but harder.
On the other hand, it's quicker to mess with the contract than with code, if you're comfortable with schemata etc. So you can do some incremental change in the contract.
Aren't there also tools that will generate a code skeleton from the WSDL? I'm almost positive there are. If so, you might do well to make the schemata the "code" item, and generate code from it.