|
Hi all,
I'm curious as to what ya'll think is the best solution for versioning the sop faults returned from the server back to the client. Is there any "best practices" available for this? I currently version my wsdl's using namespace naming, and so I plan on doing the same with soap faults. Other than making sure declaring the soap faults in its own versioned namespaces, I can't really think of any other solutions. Any suggestions? Thanks!
<rant> On a side note, I think for AXIS in particular seems to lack a good "central" fault processing mechanism. By that I mean when a fault takes place in the RPC provider, the exception is given to the registered serializers to be processed/serialized BEFORE being passed on through the onFault methods in all the handlers. Unless I've mistaken, I believe this architecture thus forces us to put versioning logic directly inside the fault serializers themselves, or to rely on handlers to modify the already serialized result. I wonder why AXIS decided not to keep this idea of a "faultlistener" that was available in Apache SOAP. </rant> |
