Hi,
I don't quite understand the purpose of this wrapper call - it seems to add complexity - while breaking the rules of soap to some degree

I've read http://drupal.org/node/147941

and seen the comment 

 
  // Replace exposed service with valid internall call. This is so ugly.. but the only way 
  // to have a callback for impossible methods, like containing . in the method name.

So I realise that it's to avoid dots in function names - but I don't get why there need to be dots in the names of registered functions...

In fact it seems that the function name exposed by soap needs to be the value of a php function - so why not just register the '#callback' value with the soap sever instead of the '#method' value? Then the soap wrapper wouldn't be needed.

I feel like I might be missing something obvious here - but maybe it's a good solution - and I'm interested to hear from other developers on this