Optimized soap content

[Taylor, Clarence B]

I am attempting to create some web services for existing legacy applications.  These applications *CAN* take hundreds of parameters but usually any given invocation will only use a few.  My initial approach was to create a java class, called InputParms, that have all of the parameters defined as private with public getter/setters.  This way when the client side, via its UI or other appropriate mechanism could set the few parameters needed for this particular service and then invoke the web-service with the InputParms class as one of the services parameters.  The service side of the code would then format the data appropriately for the legacy service.   However when the InputParms class is serialized into the soap body it becomes very large.  I am looking for a technique that is "content" driven so that only those parameters specified are sent.  Because of the large number of parameters, I hesitate to surface them in WSDL, because then the WSDL becomes more unwieldy.   I am aware that this is not an "AXIS" issue per se, however since the axis is engine is doing the serialization of the classes, I thought that perhaps others have run into this issue.  If there are other appropriate forums, pointers to them would be appreciated.   Thank you   Brad Taylor