Salesforce Developer Community

Chatter

Feed
0

Best Answers
0

Likes Received
0

Likes Given
3

Questions
4

Replies

Issue with {urn:enterprise.soap.sforce.com}ID

Why the Enterprise WSDL is trying to validate the ID type when it didn't generate the corresponding mapping class..

<service_error_message>http://localhost:9068/sls/1.0/SalesForce: cvc-simple-type 1: element {urn:sobject.enterprise.soap.sforce.com}AccountId value 'My1234' is not a valid instance of type {urn:enterprise.soap.sforce.com}ID</service_error_message>

Any helphere please..

Thanks,

Yellapa

YA
May 13, 2010
Like
0

1 replies

Why I am not able to find by account id.

I am calling a serach method using enterprise Web Service. I am able to get the resuls correct by using city name in search parameter but not able to do with account id..

Working with city name

find {Jacksonville} returning " +
           "Account(id), Opportunity(AccountId), " +
           "Contact(AccountId, Primary_Contact__c, Title, FirstName, Middle_Initial__c, LastName, Birthdate, Gender__c, OtherStreet, " +
           "Other_Address_Line_2__c, OtherCity, OtherState, OtherPostalCode, County__c, Phone, MobilePhone, " +
           "Email, MailingStreet, MailingCity, MailingState, MailingPostalCode, Marital_Status__c, Spouse_First_Name__c, " +
           "Spouse_Last_Name__c, Spouse_Date_of_Birth__c, Medicare_Eligibility_Indicator__c WHERE Primary_Contact__c = true

But Not working:

find {001S000000C0*} returning " +
           "Account(id), Opportunity(AccountId), " +
           "Contact(AccountId, Primary_Contact__c, Title, FirstName, Middle_Initial__c, LastName, Birthdate, Gender__c, OtherStreet, " +
           "Other_Address_Line_2__c, OtherCity, OtherState, OtherPostalCode, County__c, Phone, MobilePhone, " +
           "Email, MailingStreet, MailingCity, MailingState, MailingPostalCode, Marital_Status__c, Spouse_First_Name__c, " +
           "Spouse_Last_Name__c, Spouse_Date_of_Birth__c, Medicare_Eligibility_Indicator__c WHERE Primary_Contact__c = true

Any help is much appreciated. thank you..

YA
May 12, 2010
Like
0

5 replies

Generating Enterprise WSDL client using JAX-WS

I am trying to generatin Web Service client for Enterpirse WSDL using JAX-WS but getting following error.

Errors occurred during wsimport.

error: XPath evaluation of "//xsd:schema[@targetNamespace='urn:enterprise.soap.sforce.com']" results in empty target node
warning: src-resolve: Cannot resolve the name 'tns:ID' to a(n) 'type definition' component.
line 0 of file:/C:/src/SalesForce-Enterprise.wsdl#types?schema1
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 0 of file:/C:/src/SalesForce-Enterprise.wsdl#types?schema2
error: (Relevant to above error) another "DescribeLayout" is generated from here.
line 0 of file:/C:/src/SalesForce-Enterprise.wsdl#types?schema2
error: Two declarations cause a collision in the ObjectFactory class.
line 0 of file:/C:/src/SalesForce-Enterprise.wsdl#types?schema2
error: (Related to above error) This is the other declaration.
line 0 of file:/C:src/SalesForce-Enterprise.wsdl#types?schema2
error: com.sun.istack.SAXParseException2: (Related to above error) This is the other declaration.

com.sun.istack.SAXParseException2: (Related to above error) This is the other declaration.

I am using the below JAXB bindings..

<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>

Any help on this, is much appreciated.. Thaks

It might be duplicate post in the forum, sorry abou it....

YA
May 05, 2010
Like
0

3 replies

Issue with {urn:enterprise.soap.sforce.com}ID

Why the Enterprise WSDL is trying to validate the ID type when it didn't generate the corresponding mapping class..

Any helphere please..

Thanks,

Yellapa

YA
May 13, 2010
Like
0

5 replies

Generating Enterprise WSDL client using JAX-WS

I am trying to generatin Web Service client for Enterpirse WSDL using JAX-WS but getting following error.

I am using the below JAXB bindings..

Any help on this, is much appreciated.. Thaks

It might be duplicate post in the forum, sorry abou it....

YA
May 05, 2010
Like
0

16 replies

JAX-WS wsimport tool does not compile enterprise.wsdl

I am trying to get my enterprise.wsdl to compile with the wsimport tool from the latest JAX-WS release. Basically what I am trying to do is to eventually move our application away from the now pretty tired Axis 1 environment to JAX-WS which will in due course come bundled with Java 1.6.

Typical errors are like:

[wsimport] [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.
[wsimport] line 2611 of file:/home/mm/oscar/build_current/dev/jaxws/sforce/enterprise.wsdl

[wsimport] [ERROR] (Relevant to above error) another "DescribeLayout" is generated from here.
[wsimport] line 2456 of file:/home/mm/oscar/build_current/dev/jaxws/sforce/enterprise.wsdl

It seems wsimport which I believe internally uses the xjc compiler from JAXB doesn't like identical element and type names.

Have others encountered the same / similar problem? Are there simple solutions (I know I can create custom bindings for those elements but that is pretty painful)?

Thanks

malm
December 06, 2006
Like
0