Hi Vincent,

On 7/24/07, Vincent Massol <vincent@massol.net> wrote:

Hi,

If our goal is to implement the Confluence XMLRPC interface ( http://confluence.atlassian.com/display/DOC/Remote+API+Specification) then it seems to me we shouldn't throw XWikiException in any method in our ConfluenceRpcInterface interface. Several methods instead should return a boolean to indicate success or failure.

Does anyone know why we're throwing them?

Are we ok to remove all exception throwing?

I think it's better we keep those exceptions. At the moment they don't throw much informative exceptions but we could make them do so and let the RPC invoker know what went wrong. For an example, if the getSpaces() call have a problem, there would be no other way of identifying it from the client side, client will only get an empty list (of spaces), which is not correct. Any other ideas ?