[SalesForce] Metadata API WSDL Import errror

UPDATE: As it stands this doesn't actually work. You will get the message

Apex Generation Failed
No type specified for element vendorId

Most likely the issue is the missing first import that defines the data types.

I was able to get the WSDL to import and generate code by merging the content of clareityStoreFaults.xsd directly into the ClareityStore.wsdl. Note that I didn't do the same for the http://schemas.xmlsoap.org/wsdl/ import.

So the steps were:

1. Comment out <xs:import namespace="http://schemas.xmlsoap.org/wsdl/"></xs:import>
2. Comment out <xs:import namespace="http://ws.clareity.com/clareityStoreFaults" schemaLocation="clareityStoreFaults.xsd"></xs:import>
3. Paste the contents of clareityStoreFaults.xsd xs:schema element under the commented out code from step 2.
4. Import the modified WSDL into Salesforce

I haven't been able to test if it actually works against the web service, but it does import and generate code.

The Salesforce wsdl2apex tool does not support a number of WSDL features. See Supported WSDL Features

That section does say:

Apex also supports the following schema constructs:

• xsd:attribute, in Apex code saved using API version 15.0 and later

However, I've found in practice you usually get the Unsupported Schema element found error message that you encountered.

I've been working with an intern on an alternative WSDL to Apex converter to try and overcome a number of the limitations. You can get it for free from WSDL Parser and Apex Generator. Ensure you get v1.6.0 or later for WSDLs with attributes. It currently only supports Windows. (Full disclosure: I currently work for the company that creates this tool).

In this case the unsupported <xsd:attribute> elements will be skipped from the WSDL and warnings added to the resulting apex. You will need to manually enforce the 3 character limit on the hexBinary values.

Note that the Salesforce wsdl2apex tool doesn't support <xs:extension> either. We should be able to handle this by replicating the Apex members from the base class and extending the parameters passed to WebService.invoke.

If you do have further issues, can you share your WSDL via some other means (DropBox, Google Docs, etc...). It will be easier to check it as a whole.