Please can any one explain clearly what does the word BINDING in webservices world refer too. I see this used in so many places like binding WSDL to SOAP...
Thanks Ulf For the reply, from that I understand PortType is like an interface and binding basically associates a portType with message format and protocal.
Now the binding element mentioned associated soap over http protocal and message format as document to port type glossary terms.
Can you give me another example of binding which is not soap over http protocal and different message format Please??. As i find the same binding in different places and I understand that WSDL binding would let not only soap binding but something else as well?? Thanks for your help in advance
Ulf Dittmer
Marshal
Joined: Mar 22, 2005
Posts: 32767
posted
0
WSDL can in theory handle protocols other than SOAP and HTTP; however if you look at the abstract of the WSDL Spec, it says that nothing such is defined at present. Those other message formats might be Email or messaging.
The available styles are rpc/literal, rpc/encoded, document/literal and document/encoded, all of which are explained here.
There are other than soap, for example there could be EJB binding or Java binding , where the actual implementation is done in a EJB or a plain Java class respectively.
Mohamed Farouk
Ranch Hand
Joined: Jun 08, 2005
Posts: 234
posted
0
So it is good to have WSIF Clients as it would the provide the clients with a shield from servers stopping to offer any protocals or messages formats. Say initially have EJB and then later stop EJB and offer only SOAP bindings. Am i right in thinking?
As with wsif the client interacts with the service in a protocal and message format independent way?
Deepak Kaul
Greenhorn
Joined: Nov 08, 2005
Posts: 13
posted
0
You are right, using WSIF the client doesn't have to worry about how the service is actually implemented, as long as rest of the WSDL remains the same, the bindings can change without any effect on the clinet