File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Web Services and the fly likes Issues with CXF WSDL2Java Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Issues with CXF WSDL2Java" Watch "Issues with CXF WSDL2Java" New topic
Author

Issues with CXF WSDL2Java

Harry Hinch
Greenhorn

Joined: Jun 10, 2011
Posts: 1
I have a web service that I have been using for that last few years using Axis2. We are now converting our web service client to CXF. I get the following error when I try and generate the java client using WSDL2Java from CXF. Any suggestions would be appreciated. I am using version 2.2.9 of CXF

WSDLToJava Error: Non-unique body parts! In a port, operations must have unique operation signatures on the wire for successful dispatching. In port {www.servicelink.com/2010/07}CustomBinding_IWordDocMerge, operations "{www.servicelink.com/2010/07}ConvertToPDF" and "{www.servicelink.com/2010/07}MergeWordDocs" have the same request body block {www.servicelink.com/2010/07/messages}DocumentContents


I am using the following options for wsdl2java from inside of Ant




Here is the WSDL that I am trying to create a CXF client for :


Ravinderjit Singh
Ranch Hand

Joined: Jan 13, 2010
Posts: 70
It's by definition of WSI basic profile 1.1 and some more specs of
document-literal webservices.
On the wire there is only element ... no operation, no message .. only
element (one defined in message).
That's why it has to be unique, otherwise it's not possible to distinguish
between them.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Issues with CXF WSDL2Java
 
Similar Threads
Axis2 Issue, Please Help!
weblogic.webservice.tools.wsdlp.WSDLParseException: [WSDL Parser]:first element is not definitions
Java class to WSDL
JAX-WS - wsdl with operations or message that have a long parameter list
NullPointerException when calling a web service