Can somebody explain what this actually means? An example would be really helpful.
WS-I: (BP2012) A document-literal binding contains soapbind:body elements that refer to message part elements that do not have the element attribute.
Can somebody explain what this actually means? An example would be really helpful.
WS-I: (BP2012) A document-literal binding contains soapbind:body elements that refer to message part elements that do not have the element attribute.
Copyright © 2021 Jogjafile Inc.
This message is related to the WS-I Basic Profile, which attempts to clarify the subset of WSDL and other specifications that are generally interoperable.
In this case, BP2012 is associated with the following:
You would typically see this if one of the messages used in your web service is defined in terms of a
type
instead of anelement
, for example:To fix this, you will need to change your message so that the
part
is defined in terms of anelement
, something like:Alternatively, you may want to switch your web service from using a
document/literal
binding to using anrpc/literal
binding. With anrpc/literal
binding, parts are defined in terms of atype
instead of anelement
.