The current web service method signatures are of strongly-typed primitives and in complex environments risk versioning challenges. UDDI just pushes the problem into configuration/deployment management.
Please consider an optional switch for both Domain and Service web service generation that:
-
Accepts a base identifying message header
-
Uses supporting Processor / Provider / MessageHandler-Factory patterns to manage actual object payload
-
And route the business object to the appropriate strongly typed class method
Actual implementation I leave to the community to define but in general the WS-Standards for identity/routing message headers seems the logical choice.