"thomas.diesler(a)jboss.com" wrote : In that case a wsdl like this | AFAICS the requriment pertains only the the java realm and not to the abstract contract in wsdl. This is not in the BP since it only governs existing specifications namely WSDL 1.1, which does not have a mechanism to express this convention. The whole reason for the wrapped convention, is to fix the RPC style in WSDL 1.1 by overlaying the RPC requirements on top of a document/literal service. (This is the source of the operation name match requirement). So the intention is that a server component using the wrapped convention would provide hints to any client so that it would use this style as well. However since a WSDL extension was not introduced, the service still works with any thing that understands document/literal (since it is just a convention). So, by design, the wrapped convention is more restrictive than a normal document/literal bare service. The problem was fully addressed in WSDL 2.0, where the wrapped convention became the new RPC style. So, in WSDL 2.0, all of these rules and restrictions you see are officially part of the spec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001051#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...