res1st
Jul 4th, 2006, 04:31 AM
Hi,
i've wrote my wsdl and my schema(top-down). It's all working fine.
I thought about naming conventions in web services. Is there something available?
For example, how should i name my message types?
doc/literal: Name is the content, for example "airlineticketid". But if i have more than one operations i need maybe more than one "airlineticketid" message. Should i name my messages "operationname_content"?
The content name is very important, because the name will be shown in the IDE if you generate stubs.
In doc/lit wrapped (WS-I) there is always only one part of a message allowed, so all parameters (for operations with more than 1 parameter) will need a "container" object. How should i call my container?
It would be interessting if someone knows a "best practice document" or a "naming standard" about WSDL element names.
Cheers,
Ingo
Update: Of course, you can reuse the messages for more than one operation. But question still exists, is a naming standard available?
i've wrote my wsdl and my schema(top-down). It's all working fine.
I thought about naming conventions in web services. Is there something available?
For example, how should i name my message types?
doc/literal: Name is the content, for example "airlineticketid". But if i have more than one operations i need maybe more than one "airlineticketid" message. Should i name my messages "operationname_content"?
The content name is very important, because the name will be shown in the IDE if you generate stubs.
In doc/lit wrapped (WS-I) there is always only one part of a message allowed, so all parameters (for operations with more than 1 parameter) will need a "container" object. How should i call my container?
It would be interessting if someone knows a "best practice document" or a "naming standard" about WSDL element names.
Cheers,
Ingo
Update: Of course, you can reuse the messages for more than one operation. But question still exists, is a naming standard available?