On Wednesday 17 December 2008 3:49:24 pm Aaron Mulder wrote: > On Wed, Dec 17, 2008 at 2:14 PM, Daniel Kulp <[email protected]> wrote: > > Any chance you could file a JIRA and attach your test case? > > Maybe. I can't use this specific WSDL as it is from a commercial > software product and I probably don't have rights to submit it to > Apache. But I could try to paraphrase it. > > However, can you point me to the existing tests? It's just as likely > that I'm doing something wrong (for instance, in my binding file) so > I'd like to check that before I go to the trouble of building a > representative WSDL.
The binding files I looked at are in: http://svn.apache.org/repos/asf/cxf/trunk/tools/wsdlto/frontend/jaxws/src/test/java/org/apache/cxf/tools/wsdlto/frontend/jaxws/wsdl11/resources/ they are relatively simple though. Dan > > Thanks, > Aaron > > On Wed, Dec 17, 2008 at 2:14 PM, Daniel Kulp <[email protected]> wrote: > > Any chance you could file a JIRA and attach your test case? > > > > I checks our tests and we do have some tests that test these scenarios so > > I'm not sure why they wouldn't be working. Having a testcase would > > definitely help. > > > > Dan > > > > On Friday 12 December 2008 4:14:06 pm Aaron Mulder wrote: > >> 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='Hell > >>oPo rt']"> <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 > >>='H ello']"> <jaxws:parameter > >> > >> part="wsdl:definitions/wsdl:messa...@name='HelloRequest']/wsdl:pa...@nam > >>e=' 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 > > > > -- > > Daniel Kulp > > [email protected] > > http://dankulp.com/blog -- Daniel Kulp [email protected] http://dankulp.com/blog
