Okay i get it. I this case the code is generated from a WSDL, but that WSDL isn't past on by CXF. It generates it's own when published. Is there something that i'm forgetting or how can i pass on the WSDL that is used for the generation of the code?
2013/3/28 Glen Mazza <[email protected]> > On 03/28/2013 08:54 AM, Ted Roeloffzen wrote: > >> Good day all, >> >> To elaborate on my earlier mail. >> The problem is that the input and ouput typenames in de wsdl are >> incorrect. >> > > The name that is set in the Webparam-annotation of the webmethod isn't >> used. >> for the input the name of webmethod is used and for the output the name of >> the webmethod is used and gets response added to it. >> > > That sounds like Doc/Lit wrapped (rules #4 and #5 here: > http://www.ibm.com/**developerworks/webservices/**library/ws-usagewsdl/<http://www.ibm.com/developerworks/webservices/library/ws-usagewsdl/>), > which is the way WSDLs (at least doc/lit ones) should appear. I'm not > sure how to override that (or the value of doing so), as I rarely use > Java-first. Hopefully someone else can help here. > > Glen > > > > Is there a setting that i'm forgetting? >> >> kinds regards, >> >> Ted Roeloffzen >> >> >> 2013/3/28 Ted Roeloffzen <[email protected]> >> >> Good day all, >>> >>> I've created a webservice using the wsdl2java maven plugin. >>> But when I publish the webservice and check the wsdl, by going to the url >>> and adding ?wsdl, the outputted wsdl isn't the same as the one we used in >>> the wsdl2java plugin. >>> WhenI I look at the annotations above the generated classes and method, >>> they are equal to the wsdl we used for the wsdl2java plugin, but differ >>> from de wsdl that is published by the endpoint. >>> >>> Does this sound familiar to anyone or does anyone have any idea what i'm >>> doing wrong? >>> >>> kind regards, >>> >>> Ted Roeloffzen >>> >>> >>> >
