I'm normally inclined to agree with that...but...circumstances currently dictate this. I'm working on getting reduced tho.
The app in question is a VMWare management app that has a TRULY obscene number of operations available through the webservice (750 registered operations). The WSDL for it is magnificent. My next step involves refactoring the hypervisor top-level data object into sub objects (propertyCollector, performanceManager, rootFolder, etc. semi-in-line with the server's own object model) but I'm still struggling with the best method of representing that. I keep going back and forth on the best way to represent server level objects, while keeping my client-side footprint as small as possible.
Thus, my mediator is a little overweight at the moment.
I thought I would share the mapping technique, since it's a nice little way of keeping your interests and function handling in the same place (i.e. you only have to modify the one object, and voila, you get both things handled at once).