function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
EclipseTalkEclipseTalk 

enterprise.wsdl JAX-WB generation errors

Hello,

I'm using the following command to generate the java skeleton code for the enterprise.wsld

jaxws-ri/bin/wsimport.sh -p stubs -d stubs-build -s stubs-src enterprise.wsdl

 

I'm getting the following errors. Does anyone know why?

Thank you.

 

[WARNING] src-resolve: Cannot resolve the name 'ens:sObject' to a(n) 'type definition' component.
  line 2581 of file:/C:/Jazz/salesforce/jaxws-ri/bin/enterprise.wsdl#types?schema2

[ERROR] A class/interface with the same name "com.sforce.soap.enterprise.DescribeLayout" is already in use. Use a class customization to resolve this conflict.
  line 3289 of file:/C:/Jazz/salesforce/jaxws-ri/bin/enterprise.wsdl

[ERROR] (Relevant to above error) another "DescribeLayout" is generated from here.
  line 3088 of file:/C:/Jazz/salesforce/jaxws-ri/bin/enterprise.wsdl

[ERROR] Two declarations cause a collision in the ObjectFactory class.
  line 3088 of file:/C:/Jazz/salesforce/jaxws-ri/bin/enterprise.wsdl

[ERROR] (Related to above error) This is the other declaration.  
  line 3289 of file:/C:/Jazz/salesforce/jaxws-ri/bin/enterprise.wsdl

Message Edited by EclipseTalk on 08-26-2009 06:42 AM
Best Answer chosen by Admin (Salesforce Developers) 
EclipseTalkEclipseTalk
 I fixed it by using the binding below by having JAXB automatically resolve name conflicts....
<bindings
  xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns="http://java.sun.com/xml/ns/jaxws">
  <bindings
    node="//xsd:schema[@targetNamespace='urn:enterprise.soap.sforce.com']">
    <jaxb:globalBindings
      underscoreBinding="asCharInWord" />
    <jaxb:schemaBindings>
      <jaxb:nameXmlTransform>
        <jaxb:typeName
          suffix="Type" />
      </jaxb:nameXmlTransform>
    </jaxb:schemaBindings>
  </bindings>
  <enableWrapperStyle>false</enableWrapperStyle>
  <enableAsyncMapping>false</enableAsyncMapping>
</bindings>

All Answers

EclipseTalkEclipseTalk
 I fixed it by using the binding below by having JAXB automatically resolve name conflicts....
<bindings
  xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns="http://java.sun.com/xml/ns/jaxws">
  <bindings
    node="//xsd:schema[@targetNamespace='urn:enterprise.soap.sforce.com']">
    <jaxb:globalBindings
      underscoreBinding="asCharInWord" />
    <jaxb:schemaBindings>
      <jaxb:nameXmlTransform>
        <jaxb:typeName
          suffix="Type" />
      </jaxb:nameXmlTransform>
    </jaxb:schemaBindings>
  </bindings>
  <enableWrapperStyle>false</enableWrapperStyle>
  <enableAsyncMapping>false</enableAsyncMapping>
</bindings>
This was selected as the best answer
LearnerSFLearnerSF

I had the same problem, and your fix resolved 4 of the 5 errors that I received. However, I still get this error:

 

[WARNING] src-resolve: Cannot resolve the name 'ens:sObject' to a(n) 'type definition' component.

 

 
Ezio_2010Ezio_2010

EY you, the guy with the  src-resolve: Cannot resolve the name 'ens:sObject' error, it is not an error it is a warning, f/"($ing annoying for sure, did u manage to send this warning to hell?

 

let me know, im trying the same stuff, the same f"($/ing stuff and the same errors that arise!!!

 

tired of IT 

Keith654Keith654

Here is a summary article that may be of help if you are hitting this problem and a couple of others:

 

http://force201.wordpress.com/2011/02/06/quick-summary-of-how-to-get-started-with-the-enterprise-wsdl-api-via-javas-jaxb/

 

Keith