I was playing around with a JAX-WS/JAXB binding file for a real ugly
WSDL -- just trying to rename various classes, methods, parameters,
etc. to make them more readable. I used the Maven plugin for
wsdl2java.
I did OK changing the service interface class name, service class
name, operation method name on the service interface, and JAXB classes
(like the argument types to the service operation).
I was not able to change the "getPortType" method name on the service
class. I followed this example in the bindings schema (putting in the
right service name and port name from the WSDL):
<jaxws:bindings
node="wsdl:definitions/wsdl:servi...@name='Hello']/wsdl:po...@name='HelloPort']">
<jaxws:method name="getCustomizedPort"/>
</jaxws:bindings>
But that just seemed to be ignored.
I also was not able to change the parameter names for the operation.
It has like 4 input args and 5 output args, so it ends up with a
method like:
public void doSomething(In1 i1, In2 i2, ..., @WebParam(mode =
WebParam.Mode.OUT...) Out1 o1, Out2 o2, ...)
I tried following this example in the bindings schema (again, putting
in the right port type name, operation name, message name, and
argument type name):
<jaxws:bindings
node="wsdl:definitions/wsdl:portty...@name='Hello']/wsdl:operati...@name='Hello']">
<jaxws:parameter
part="wsdl:definitions/wsdl:messa...@name='HelloRequest']/wsdl:pa...@name='parameters']"
childElementName="types1:argument" name="helloArgument"/>
</jaxws:bindings>
But that was ignored. I'm not sure what I would have put in place of
"types1" in any case. And I assume "argument" is the element name
within the complex type for the request message parameters element?
Are these results expected or should these other overrides work too?
Thanks,
Aaron
