Pierre-Yves Varoux schrieb:
And why not re-generating exception by parsing the message exception ?
Because it almost seems like a hack. I just thought there was probably a more proper way to do it. But maybe there isn't :)
Yes... Exceptions are a java mechanism and xmlrpc must be interoperant (with fault codes).
Not precise java mechanism only. Exceptions are known in every good OOP-language. The problem is:
a) not all XMLRPC implementations run on OOP languages b) not all these languages, if OOP have Exceptions c) not all wich have Excptions can have subclasses of them d) if all the above, how should the client know the type of the exception based on a name, when it does not share the implementation (same base classes for Exceptions) with the host?
The only solution I would see so far is to implement a common set of Exception types for which the server is responsible to identyfy and map to and a matching implementation on client side.
Regards Tino
