Specifying messaging properties in WSDL
Stefan writes about Strongly Typed Message Properties in Web Services. I agree. The place to articulate message properties is in policy which may be attached to WSDL.
The reason for this separation of concerns is important. You might have a standardized WSDL, blessed by some vertical industry standards org, (that you can't change) which simply specifies the application-level message exchange content, not any QoS, security, etc. How do you tell your partner that your service uses a standard WSDL description AND communicate your QoS requirements, etc.? The answer is WS-PolicyAttachment. By preserving the separation of concerns, the WSDL can be more readily reused.
The reason for this separation of concerns is important. You might have a standardized WSDL, blessed by some vertical industry standards org, (that you can't change) which simply specifies the application-level message exchange content, not any QoS, security, etc. How do you tell your partner that your service uses a standard WSDL description AND communicate your QoS requirements, etc.? The answer is WS-PolicyAttachment. By preserving the separation of concerns, the WSDL can be more readily reused.
posted by Chris at
Tuesday, May 18, 2004
|
0 comments
0 Comments:
Post a Comment
<< Home