While reading the 3rd part of the factored WS-Addressing spec, it occurred to me that the discussion on how to associate wsa:action headers with messages in WSDL operations or how to implicitly generate them could be simplified by having just a uniform action for all SOAP messages:
wsa:action="process:message"
Anything more in the action header may result into consumers making assumptions about the internal dispatching mechanics of the service (wsa:action as the new way to do RPC). Also, there may be a case that consumers will make assumptions about the semantics of the processing of the message based on the wsa:action header rather than the contents of the message body and the interaction protocol.
I really think that wsa:action should be left out 🙂
Last week, I wrote about the evolution of the CVOYA Graph. After a lot of…
Last year, I released the "Graph Model" library for .NET as an open source project. It…
Today I'm pushing Spring Voyage out of the harbor. You can track its journey on…
In my last post, I wrote that "the typing of code was parallelized and delegated.…
In February, I wrote about the small team I'd stood up instead of hiring humans:…
Assembling a dream team without a single hire I've been making great progress on CVOYA's…