com.sforce.ws.ConnectionException: Unexpected element #35
Comments
|
You have to use the API endpoint version# that matches the WSDL you used, On Thu, Oct 17, 2013 at 12:12 PM, earlofrose notifications@github.comwrote:
|
|
Thanks for commenting so quickly! We were only mixing and matching for discovery and testing. Our most recent builds (which include this failure) are failing on DescribeLayoutResult layout = ecn.describeLayout(sfObject, recTypeIds). This was a v29 wsdl, v29 endpoint and used the wsc#29 to build the client. Thanks, |
|
Also, I believe this is a problem with the WSDL generation on salesforce.com's side. It's marking things as required (minOccurs = 1 or no minOccurs set, which defaults it to 1 in WSC) that are not being returned in their responses. |
|
Can you double check that you're really using the v29 endpoint, as from my quick testing so far with describeSObject, i haven't seen it not return compactLayoutable yet. IIRC, WSC has an option to do wire logging, which might be helpful. |
|
and also which specific sobject you're seeing this with. |
|
describeSObject works with v29. describeLayout is what fails with v29. Here's the exception, relevant portion of the wsdl and the a piece of the response showing the lack of iconURL. EXCEPTION RESPONSE WSDL |
|
Here's the WSDL and RESPONSE.... markup WSDL: <complexType name="DescribeQuickActionListItemResult"> RESPONSE: |
|
Thanks, yeah, I'm seeing the same thing. |
|
I'll follow up with the salesforce team that owns the DescribeQuickAction On Thu, Oct 17, 2013 at 2:52 PM, Simon Fell notifications@github.comwrote:
|
|
Fantastic! Thanks, guys. Sent from my iPhone On Oct 17, 2013, at 5:26 PM, "Jeff Lai" <notifications@github.commailto:notifications@github.com> wrote: I'll follow up with the salesforce team that owns the DescribeQuickAction On Thu, Oct 17, 2013 at 2:52 PM, Simon Fell <notifications@github.commailto:notifications@github.com>wrote:
— |
|
hey jefflai - can you give any kind of update on this? (has someone accepted it as an issue, maybe started a bug for tracking?) |
|
I had the same problem and I fix it by updating the authEndPoint hope this will help. |
|
thanks for the suggestion. so, you updated the endpoint by adding a '/'? not sure how that would affect the meta-data thats being returned from the calls? i tried it anyway with same results. |
|
@earlofrose @dwfallin a patch to fix this issue on the server side was deployed. Please reopen if you are still experiencing this issue |
Using the WSC#29, we receive the following error when trying to call the DescribeSObjectResult ds = ecn.describeSObject(sfObject); and a similar error when trying to call DescribeLayoutResult layout = ecn.describeLayout(sfObject, recTypeIds); depending on whether we use the v25 or v29 endpoint. We were able to work around this issue using the lax-minoccurs-checking JVM switch. It appears that elements that are not required (not being sent in responses from salesforce) are mistakenly being marked as minOccurs = 1, either through it not being specified or being directly marked as minOccurs = 1.
Exception details:
com.sforce.ws.ConnectionException: Unexpected element. Parser was expecting element 'urn:enterprise.soap.sforce.com:compactLayoutable' but found 'urn:enterprise.soap.sforce.com:createable'
at com.sforce.ws.bind.TypeMapper.verifyTag(TypeMapper.java:387)
at com.sforce.ws.bind.TypeMapper.verifyElement(TypeMapper.java:416)
at com.sforce.soap.enterprise.DescribeSObjectResult.loadFields(DescribeSObjectResult.java:803)
at com.sforce.soap.enterprise.DescribeSObjectResult.load(DescribeSObjectResult.java:787)
at com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:629)
at com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:505)
at com.sforce.soap.enterprise.DescribeSObjectResponse_element.loadFields(DescribeSObjectResponse_element.java:67)
at com.sforce.soap.enterprise.DescribeSObjectResponse_element.load(DescribeSObjectResponse_element.java:58)
at com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:629)
at com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:505)
at com.sforce.ws.transport.SoapConnection.bind(SoapConnection.java:172)
at com.sforce.ws.transport.SoapConnection.receive(SoapConnection.java:146)
at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:110)
at com.sforce.soap.enterprise.EnterpriseConnection.describeSObject(EnterpriseConnection.java:547)
at org.stjude.crm.EventProxy.listSFPickListItems(EventProxy.java:982)
at org.stjude.crm.EventProxy.listSuffixes(EventProxy.java:3686)
at org.stjude.events.ui.controllers.AbstractControllerBase.getSuffixes(AbstractControllerBase.java:257)
The text was updated successfully, but these errors were encountered: