I'm plowing through the mountain of standards relating to web services. One that is interesting to me and that I'm kind of on the fence on is WS-Addressing. I am curious to what others think about this. I can see some of benefits especially the address (endpoint) and reply-to parts. But I can also see increasing the complexity for the developers by requiring them to know a lot more about the implementation than they had with just a simple URL.
Without WS-Addressing, the developers just implemented their web services consumer with the provided WSDL which basically was just manipulating objects in their native format (Pretty easy stuff assuming you are using Doc/Literal). With WS-Addressing they would be required to populate the header of the SOAP message. This is not contained within the WSDL. It does requires more in-depth understanding of the SOAP message structure. Of course I guess that they will have to learn sooner or later based upon the other WS-I standards coming out. Either that or run away screaming, kind of like J2EE.
I'm wondering from a practical (not purist) standpoint if implementation based upon some other method is not better? What does everyone think? WS-Addressing the way to go? Or is it too much added on to the developer? By the way I use an intermediary or middleware layer as the entry point, I don't allow point-to-point connections or interfaces.