I agree with Corrinne. Option D is the way to go. Although, I have to say, the other options sound like they belong in a superhero technical service contract. 'Captain WSDL, assemble!'
Option D is definitely the winner. You can't just assume WSDL is the only way to define a service contract these days. There are so many options, gotta keep an open mind!
Hmm, I'm not so sure. I've seen components and HTTP methods used in service contracts too, depending on the technology. Maybe option D is the safest bet?
Cordie
2 months agoAbel
9 days agoBea
23 days agoVerda
30 days agoJennifer
1 months agoTarra
1 months agoMollie
1 months agoCorrinne
2 months agoSelma
2 months agoElfrieda
2 months agoLezlie
1 months agoDorian
1 months agoAlyce
2 months agoJesus
2 months agoDesmond
2 months ago