|
Yes ebMS3 can be used can be used when viewing the interaction as a WS service described by WSDL. ebMS3 has its own header to add to the SOAP envelope header section, and reuses WSS and WS Reliabilty or ReliableMessaging headers and I suppose most any other
WS-* headers when they make sense (to use!) Then ebMS3 could have a WSDL for a doc-literal request response service, for example. Unlike WS, however, ebMS separates out the security, transport, message or data metadata parts of a service from the SOAP body (so attachments if adding attachments).
For non soap-with-attachment messages, the WSDL would have to add the interface/porttype/operation information and then add on XML type or elements (depending on the wsdl version) to describe the “content” of the service. I probably have examples somewhere, but I will have to go to my archive drive at home to find them. Is this enough to get you started? Dale Moberg From: Denis Nikiforov [mailto:denis.nikif@gmail.com]
Hello! Is it possible to use WSDL to describe ebMS-services? Could you provide an example? Thanks! |