Ignore:
Timestamp:
Dec 3, 2008 9:41:58 AM (15 years ago)
Author:
Ted Faber <faber@…>
Branches:
axis_example, compt_changes, info-ops, master, version-1.30, version-2.00, version-3.01, version-3.02
Children:
375ca67
Parents:
46a0f7a
Message:

Differentiate between a failure to connect to a service and the service being
provided using an unexpected protocol. Deal with the internal connection error
more cleanly when the connection is being made to an internal service. That
is, when an internal service is down, propagate a clean error out to the
caller. Before this change, the internal service failure would look like a
protocol error on the external service (SOAP being provided by XMLRPC, for
example) and try the other protocol, which would fail with a misleading error.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • fedd/fedd_types.xsd

    r46a0f7a r9d3e646  
    638638          <xsd:enumeration value="6"/>  <!-- partial instantiation -->
    639639          <xsd:enumeration value="7"/>  <!-- federant error -->
     640          <xsd:enumeration value="8"/>  <!-- connect error -->
    640641        </xsd:restriction>
    641642      </xsd:element>
Note: See TracChangeset for help on using the changeset viewer.