Permalink
Commits on Feb 13, 2017
  1. Version bump to 0.8.3

    eugenebolshakov committed Feb 13, 2017
  2. Merge pull request #24 from merhard/master

    Hopefully increased flexibility of WSDL parser by making `NullType#element` return instance of `NullElement`
    
    If the parser can't determine the type of a WSDL element and returns an instance of `NullType`, this change should allow child elements of that element to work too in simple cases.
    eugenebolshakov committed on GitHub Feb 13, 2017
Commits on Feb 10, 2017
Commits on Jun 13, 2016
Commits on Jun 10, 2016
  1. Version bump to 0.8.2

    eugenebolshakov committed Jun 10, 2016
  2. Added basic LolSoap::Builder#pretty_print

    This method is called when PrettyPrint is used and if it's not defined Builder
    just adds an xml element
    
    #17
    akostadinov committed with eugenebolshakov Jun 8, 2016
Commits on Mar 16, 2016
  1. Version bump to 0.8.1

    eugenebolshakov committed Mar 16, 2016
  2. Removed the hack for "tns" namespaces

    We don't actually need any special handling for it, the confusion was caused by
    an invalid WSDL
    eugenebolshakov committed Mar 16, 2016
Commits on Mar 2, 2016
  1. Version bump to 0.8.0

    eugenebolshakov committed Mar 2, 2016
  2. Support referenced attribute groups

    Attributes can be defined like this:
    
    ```
    <attributeGroup name="someAttributeGroup">
      <attribute name="someAttribute" />
    </attributeGroup>
    <attributeGroup name="anotherAttributeGroup">
      <attribute name="anotherAttribute" />
    </attributeGroup>
    <complexType name="someType">
      <attributeGroup ref="someAttributeGroup" />
      <simpleContent>
        <extension>
          <attributeGroup ref="anotherAttributeGroup" />
        </extension>
      </simpleContent>
    </complexType>
    ```
    eugenebolshakov committed Feb 24, 2016
Commits on Feb 24, 2016
  1. Use namespaces when looking up definitions

    There may be types, elements, etc with the same name under different namespaces,
    so we need to use namespaces when looking them up.
    eugenebolshakov committed Feb 24, 2016
Commits on Nov 12, 2015
  1. Version bump to 0.7.0

    eugenebolshakov committed Nov 12, 2015
Commits on Nov 11, 2015
  1. Support element references in type definitions

    A type definition can have an element specified like this:
    
    ```
    <element ref="tns:someElement" maxOccurs="unbounded"/>
    ```
    
    where 'someElement' is the name of an element definied in the schema.
    eugenebolshakov committed Nov 11, 2015
  2. Handle operations with multipart header/body

    Before the change we assumed that WSDL operation's header or body consists of
    one element only, whereas they can actually consist of multiple elements, e.g.:
    
    ```
    <operation name="GetTradePrice">
      <input>
        <header use="literal" part="header"/>
        <header use="literal" part="header2"/>
        <body use="literal" parts="body"/>
      </input>
    </operation>
    
    <message name="GetTradePrice">
      <part name="header" element="tradePriceRequestHeader"/>
      <part name="header2" element="authentication"/>
      <part name="body" element="tradePriceRequest"/>
    </message>
    
    ```
    
    If a header of body consists of one element though, we still build that element
    automatically for convenience and backward compatibility, e.g.:
    
    ```
    request = client.request('GetTradePrice')
    
    request.header do |header|
      # In case of multiple header or body elements they need to be specified
      # explicitly
      header.authentication do |auth|
        # something
      end
    
      header.tradePriceRequestHeader do |h|
        # something
      end
    end
    
    request.body do |body|
      # There is only one body element, so it's already built and there is no need
      # to call body.tradePriceRequest
      body.something do |something|
        # something
      end
    end
    ```
    eugenebolshakov committed Nov 9, 2015
Commits on Nov 6, 2015
  1. Handle multipart messages in WSDL

    Before the change we assumed that wsdl messages contain only one part and that
    part is the body element. In reality messages may contain multiple parts, e.g.
    header and body.
    eugenebolshakov committed Nov 6, 2015
Commits on Mar 12, 2015
  1. Get rid of jeweler

    It's not maintained, switch to the bundler style
    jonleighton committed Mar 12, 2015
  2. Fix development dependency

    jonleighton committed Mar 12, 2015
  3. Version bump to 0.6.1

    jonleighton committed Mar 12, 2015
  4. Specify encoding explicitly in the XML declaration

    This should prevent mistakes where the request content has a different
    encoding to what goes in the header.
    jonleighton committed Mar 12, 2015
  5. Fix Ruby 2.2 warnings

    jonleighton committed Mar 12, 2015
  6. Remove Gemfile.lock from git

    We should be testing with the latest dependencies; if they don't work
    then the dependency restrictions should be changed.
    jonleighton committed Mar 12, 2015
Commits on Sep 23, 2014
  1. Version bump to 0.6.0

    eugenebolshakov committed Sep 23, 2014
  2. Support SOAP Header types

    There may be a type definition for the header and we need to know what
    it is to be able to generate a header element.
    eugenebolshakov committed Sep 23, 2014
Commits on Dec 10, 2013
  1. Version bump to 0.5.1

    jonleighton committed Dec 10, 2013
  2. Version bump to 0.5.0

    jonleighton committed Dec 10, 2013
  3. Generate namespace prefixes

    Avoids conflicts which can arise when relying on the prefixes which
    existing the wsdl.
    jonleighton committed Dec 9, 2013
Commits on Dec 9, 2013
  1. Version bump to 0.4.2

    jonleighton committed Dec 9, 2013
  2. Improve soap version detection

    The soap 1.2 namespace might be present but unused
    jonleighton committed Dec 9, 2013
Commits on Oct 22, 2013