Thanks Daniel for your help.
I've tried to re-generate the client with the following configuration in
pom.xml :
<wsdlOption>
<wsdl>${basedir}/src/main/resources/de.wsdl</wsdl>
<extraargs>
<extraarg>-xjc-Xts</extraarg>
<extraarg>-autoNameResolution</extraarg>
<extraarg>-bareMethods=executeQuery</extraarg>
</extraargs>
</wsdlOption>
And it did work !
Thanks a lot !
Thomas.
On Tue, Jul 15, 2014 at 6:58 PM, Daniel Kulp <[email protected]> wrote:
>
> I’m not really sure what’s “wrong” yet. That method SHOULD be detected as
> having to be a “BARE” method and not unwrapped to individual params. For
> some reason, that detection isn’t triggering so it’s trying to unwrap the
> XmlExecuteQuery object, but since XmlExecuteQuery cannot be unwrapped, it’s
> not ending up with anything.
>
> The “simple” workaround for now would be to add
> <bareMethods><bareMethod>executeQuery</bareMethod></bareMethods> to the
> configuration to force it into that mode. That shouldn’t be required as
> the detection should detect it, but that should at least get you moving.
>
> Dan
>
>
> On Jul 15, 2014, at 12:36 PM, Thomas Manson <[email protected]>
> wrote:
>
> > Sorry,
> >
> > here is the full WSDL (and plenty of other ones)
> >
> >
> https://drive.google.com/file/d/0Bz-ZrfMHlBlHWWhxOURDOFNISW8/edit?usp=sharing
> >
> > Thanks,
> > Thomas.
> >
> >
> > On Tue, Jul 15, 2014 at 5:27 PM, Daniel Kulp <[email protected]> wrote:
> >
> >> We’d need the full WSDL and all the imports what you have is missing
> some
> >> stuff. The first missing one is comexception.xsd.
> >>
> >> Dan
> >>
> >>
> >>
> >> On Jul 15, 2014, at 11:20 AM, Thomas Manson <[email protected]
> >
> >> wrote:
> >>
> >>> Hi Daniel,
> >>>
> >>> it's attached to my first mail (on the other post), but maybe it has
> been
> >>> removed by the mailing list system.
> >>>
> >>> You can get it here :
> >>>
> >>>
> >>
> https://drive.google.com/file/d/0Bz-ZrfMHlBlHc3JIUVFqclBfcHZVSFFNQUxxMVR4SEFtWVJV/edit?usp=sharing
> >>>
> >>> Here is the original email :
> >>>
> >>>
> >>> #######################################################################
> >>>
> >>> Hi CXF !
> >>>
> >>>
> >>> I'm using CXF 2.7.0 to generate the client for the attached WSDL
> (de.zip)
> >>> with the following options :
> >>>
> >>> <wsdlOption>
> >>> <wsdl>${basedir}/src/main/resources/de.wsdl</wsdl>
> >>> <extraargs>
> >>> <extraarg>-xjc-Xts</extraarg>
> >>> <extraarg>-autoNameResolution</extraarg>
> >>> </extraargs>
> >>> </wsdlOption>
> >>>
> >>> The generated client is missing argument on one operation, while if I
> use
> >>> SOAPUI or another priopriatery tool, I can see the arguments.
> >>>
> >>>
> >>>
> >>> For example, with SOAPUI 4.5.2 :
> >>> <soapenv:Envelope xmlns:soapenv="
> >> http://schemas.xmlsoap.org/soap/envelope/";
> >>> xmlns:res="http://resourcequery.api.de.n2.tibco.com";>
> >>> <soapenv:Header/>
> >>> <soapenv:Body>
> >>> <res:executeQuery model-version="-1" implementation="1">
> >>> <query>resource(name='tibco-admin')</query>
> >>> </res:executeQuery>
> >>> </soapenv:Body>
> >>> </soapenv:Envelope>
> >>>
> >>>
> >>> CXF generated client the following :
> >>>
> >>> public interface ResourceQueryService { /**
> >>>
> >>> * Execute a Resource Query Language (RQL) query to find a set of
> >>> resources that match specific criteria.
> >>>
> >>> */
> >>>
> >>> @WebResult(name = "resource", targetNamespace = "")
> >>>
> >>> @RequestWrapper(localName = "executeQuery", targetNamespace = "
> >>> http://resourcequery.api.de.n2.tibco.com";, className
> >>> = "com.tibco.n2.common.organisation.api.XmlExecuteQuery")
> >>>
> >>> @WebMethod(action = "executeQuery")
> >>>
> >>> @ResponseWrapper(localName = "executeQueryResponse", targetNamespace
> >> = "
> >>> http://resourcequery.api.de.n2.tibco.com";, className
> >>> ="com.tibco.n2.de.api.resourcequery.ExecuteQueryResponse")
> >>>
> >>>
> >>> public
> >> java.util.List<com.tibco.n2.de.api.resourcequery.XmlSimpleResource>
> >>> executeQuery() throws InvalidQueryFault, SecurityFault,
> >>> InvalidOrgModelVersionFault, NoSuchNamedEntityFault,
> >>> InvalidServiceRequestFault, InternalServiceFault;
> >>>
> >>> }
> >>>
> >>> where you can see that the executeQuery() has no argument.
> >>>
> >>> Any idea what's going wrong ?
> >>>
> >>> I would rather not touch the WSLD, so I wonder if there's some options
> >>> available on CXF that would allow the parameters to be generated.
> >>>
> >>> What's weird is that there's other method signature quite more complexe
> >>> that are generated successfully.
> >>>
> >>>
> >>> I'll try to generated the client with the latest version of CXF, but
> last
> >>> time I tried, It failed... (expected another thread for me on this
> >> subject
> >>> then ;))
> >>>
> >>>
> >>> Thanks for your help,
> >>>
> >>> Thomas.
> >>>
> >>>
> >>> On Tue, Jul 15, 2014 at 3:13 PM, Daniel Kulp <[email protected]> wrote:
> >>>
> >>>>
> >>>> We’d need to see the WSDL.
> >>>>
> >>>> Dan
> >>>>
> >>>>
> >>>> On Jul 15, 2014, at 9:06 AM, Thomas Manson <
> [email protected]>
> >>>> wrote:
> >>>>
> >>>>> Thanks Daniel,
> >>>>>
> >>>>> Removing this dependencies did solve the problem.
> >>>>>
> >>>>> However, going for CXF 2.7.11 didn't solve my original problem
> >> described
> >>>>> in this post:
> >>>>>
> >>>>> CXF do not generate operation parameters
> >>>>>
> >>>>> where the arguments of a method is not generated with CXF while it's
> >>>> usable
> >>>>> in SAOPUI and one other propriatary tool.
> >>>>>
> >>>>> Can you have a look ?
> >>>>>
> >>>>> Thanks,
> >>>>> Thomas.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Fri, Jul 11, 2014 at 9:21 PM, Daniel Kulp <[email protected]>
> wrote:
> >>>>>
> >>>>>>
> >>>>>> Remove the cxf-common-utilities dependency entirely. That hasn’t
> >> existed
> >>>>>> for a long time.
> >>>>>>
> >>>>>> Dan
> >>>>>>
> >>>>>>
> >>>>>> On Jul 11, 2014, at 11:03 AM, Thomas Manson <
> >> [email protected]
> >>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> I'm trying to use a newer version of CXF to generate a client to
> see
> >> if
> >>>>>> it solves an issue that I have with 2.7.0.
> >>>>>>>
> >>>>>>>
> >>>>>>> I don't know where to find the equivalent of the following library
> >> used
> >>>>>> in my pom.xml :
> >>>>>>>
> >>>>>>> <groupId>org.apache.cxf</groupId>
> >>>>>>> <artifactId>cxf-codegen-plugin</artifactId>
> >>>>>>>
> >>>>>>> <dependencies>
> >>>>>>>
> >>>>>>> <dependency>
> >>>>>>> <groupId>org.apache.cxf.xjcplugins</groupId>
> >>>>>>> <artifactId>cxf-xjc-ts</artifactId>
> >>>>>>> <version>2.6.1</version>
> >>>>>>> </dependency>
> >>>>>>> <dependency>
> >>>>>>> <groupId>org.apache.cxf</groupId>
> >>>>>>> <artifactId>cxf-common-utilities</artifactId>
> >>>>>>> <version>2.5.10</version>
> >>>>>>> </dependency>
> >>>>>>> <dependency>
> >>>>>>> <groupId>org.apache.cxf</groupId>
> >>>>>>> <artifactId>cxf-rt-databinding-jaxb</artifactId>
> >>>>>>> <version>2.7.5</version>
> >>>>>>> </dependency>
> >>>>>>> </dependencies>
> >>>>>>>
> >>>>>>> I've checked cxf-common-utilities on maven repo, it's one year old
> in
> >>>>>> its last version 2.5.11, while CXF 2.7.11 has been released in April
> >>>> this
> >>>>>> year.
> >>>>>>>
> >>>>>>> Could you help me to sort out which version/maven artifact I should
> >> use
> >>>>>> to have a consistent configuration and use the very last version of
> >> the
> >>>>>> 2.7.X branch ?
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Thomas.
> >>>>>>>
> >>>>>>> <pom.xml>
> >>>>>>
> >>>>>> --
> >>>>>> Daniel Kulp
> >>>>>> [email protected] - http://dankulp.com/blog
> >>>>>> Talend Community Coder - http://coders.talend.com
> >>>>>>
> >>>>>>
> >>>>
> >>>> --
> >>>> Daniel Kulp
> >>>> [email protected] - http://dankulp.com/blog
> >>>> Talend Community Coder - http://coders.talend.com
> >>>>
> >>>>
> >>
> >> --
> >> Daniel Kulp
> >> [email protected] - http://dankulp.com/blog
> >> Talend Community Coder - http://coders.talend.com
> >>
> >>
>
> --
> Daniel Kulp
> [email protected] - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
