Masoud,
I have heard of this RPC/encoded and Document/Literal patterns.... Can i get some more detail on these patterns... I mean which one is the preferred 1.
Hi
First of all
you should consider that a WSDL describe A web service .
SOAP messages describe binding to a Service
binding could be Encoded or Literal
invoking the service could be in RPC mode or document centeric Mode.
so SOAP files could be Encoded or Literal ,thus we have 4type/style to have web services exposed to outside world/implemented
1.RPC/encoded
2.Document/encoded
3.RPC/literal
4.Document/literal
Another pattern is Document Wrapped which is a Microsoft Format , thre is no Spec for this one and
AFAIK pople who want to implemet WS frameworks should find its specs by reverse eng.
by the way :
from the 4 above type :
1-in RPC encoded everything -SOAP and WSDL are easy to read- is straightforward , but you have problem in Interoperability ,Validation ...
2-Document encoded has no use
3-RPC/literal is straightforward but still validation of message is a prob . and it is WS-I compliant
4-Document literal is the most known binding/use . it is WS-i compliant. in this mode WSDL filed are complicated and hard to read by human
in a brief :
if you are going to implement some WEB service then you should (its better to) use Document/literal or
Document Wrapped because this two mode are supported in both .Net and Java wordl. these are WS-I compliant.
JAXRPC support all except Document/encoded which has not any use.
AXIS in version 1 (AFAIR) suports RPC/encoded but in 1.2 it supports document/literal too.
I have not go with thier Performance , sure you can find more and more details on the web about both performance and more description of this models :
i suggest you look at :
http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/index.html