Skip to content

Mapping ruby Hash to XML seems to depend on order of inserting keys #859

@dazza-codes

Description

@dazza-codes

It seems that a ruby hash enumerates by the order of inserting keys (is that right?)

When composing params for a SOAP message using a Hash, we are getting SOAPFault errors related to XSD validation failures that depend on the order of XML elements. We cannot insert new key:value pairs into a Hash because it seems to mess up the resulting XML element order.

How does savon map the Hash key:value pairs to XML elements? Can it use the WSDL to correctly pluck out the key:value pairs in the correct order?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions