Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As far as I know there is not such stuff as per the SOAP/WSDL standard. But tools exists to cope with such issues. For instance, in Glassfish you can specify <strong>XSL</strong> stylesheet to transform the request/response of a web service. Other solution such as Oracle SOA suite offer much more elaborated tools to manage versioning of web service and integration of component together. Message can be <strong>routed</strong> automatically to different version of a web service and/or <strong>transformed</strong>. You will need to check what your target infrastructure offers.</p> <p><strong>EDIT</strong>:</p> <p>XML and XSD is more flexible regarding evolution of the schema than types and serialization in object-oriented languages. Some stuff can be made backward compatible by simply declaring them as optional, e.g.</p> <ul> <li><em>Adding parameters to existing functions</em> - if a parameter is optional, you get a <code>null</code> value if the client doesn't send it</li> <li><em>Adding variables to existing structure that are used in existing functions</em> - if the value is optional, you get <code>null</code> if the client doesn't provide it</li> <li><em>Removing functions</em> - no magic here</li> <li><em>Removing parameters from existing functions</em> - parameters sent by the client will be superfluous according to the new definition and will be omitted</li> <li><em>Removing variables from existing structure that are used in existing functions</em> - I don't know in this case</li> <li><em>Changing the type of a parameter used in an existing function</em> - that depends on the change. For a simple type the serialization/deserialization may still work, e.g. String to int.</li> </ul> <p>Note that I'm not 100% sure of the list. But a few tests can show you what works and what doesn't. The point is that XML is sent over the wire, so it gives some flexibility. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload