Changeset 5858c72 for fedd/wsdl


Ignore:
Timestamp:
Jun 5, 2009 3:52:45 PM (16 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:
4e7cf7b
Parents:
f4cc4b7
Message:

axis didn't like the layout of these WSDL files - presumably the multiple imports across related namespaces. This unified file seems to be parsable and probably is more portable. Some syntax differences in the fault definitions that ZSI glossed over have been corrected as well.

Location:
fedd/wsdl
Files:
4 deleted
2 edited

Legend:

Unmodified
Added
Removed

  • fedd/wsdl/fedd.wsdl

    rf4cc4b7 r5858c72  
    22<definitions name="fedd"
    33  targetNamespace="http://www.isi.edu/faber/fedd.wsdl"
    4   xmlns:tns="http://www.isi.edu/faber/fedd_messages"
    5   xmlns:bns="http://www.isi.edu/faber/fedd_bindings"
     4  xmlns:tns="http://www.isi.edu/faber/fedd.wsdl"
    65  xmlns:xsd1="http://www.isi.edu/faber/fedd_types"
    76  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    87  xmlns="http://schemas.xmlsoap.org/wsdl/">
    9  
    10   <import namespace="http://www.isi.edu/faber/fedd_types"
    11     location="fedd_types.xsd"/>
    12 
    13   <import namespace="http://www.isi.edu/faber/fedd_messages"
    14     location="fedd_messages.wsdl"/>
    15 
    16   <import namespace="http://www.isi.edu/faber/fedd_bindings"
    17     location="fedd_bindings.wsdl"/>
     8
     9   <import namespace="http://www.isi.edu/faber/fedd_types"
     10         location="fedd_types.xsd"/>
     11  <!--
     12  The message definitions are all simple embeddings of one of the types
     13  from fedd_types.xsd
     14  -->
     15  <message name="RequestAccessRequestMessage">
     16    <part name="RequestAccessRequestBody" type="xsd1:requestType"/>
     17  </message>
     18
     19  <message name="RequestAccessResponseMessage">
     20    <part name="RequestAccessResponseBody" type="xsd1:responseType"/>
     21  </message>
     22
     23  <message name="ReleaseAccessRequestMessage">
     24    <part name="ReleaseAccessRequestBody" type="xsd1:releaseRequestType"/>
     25  </message>
     26
     27  <message name="ReleaseAccessResponseMessage">
     28    <part name="ReleaseAccessResponseBody" type="xsd1:releaseResponseType"/>
     29  </message>
     30  <message name="CreateRequestMessage">
     31    <part name="CreateRequestBody" type="xsd1:createRequestType"/>
     32  </message>
     33
     34  <message name="CreateResponseMessage">
     35    <part name="CreateResponseBody" type="xsd1:createResponseType"/>
     36  </message>
     37
     38  <message name="VtopoRequestMessage">
     39    <part name="VtopoRequestBody" type="xsd1:vtopoRequestType"/>
     40  </message>
     41
     42  <message name="VtopoResponseMessage">
     43    <part name="VtopoResponseBody" type="xsd1:vtopoResponseType"/>
     44  </message>
     45
     46  <message name="VisRequestMessage">
     47    <part name="VisRequestBody" type="xsd1:visRequestType"/>
     48  </message>
     49
     50  <message name="VisResponseMessage">
     51    <part name="VisResponseBody" type="xsd1:visResponseType"/>
     52  </message>
     53
     54  <message name="InfoRequestMessage">
     55    <part name="InfoRequestBody" type="xsd1:infoRequestType"/>
     56  </message>
     57
     58  <message name="InfoResponseMessage">
     59    <part name="InfoResponseBody" type="xsd1:infoResponseType"/>
     60  </message>
     61
     62
     63  <message name="TerminateRequestMessage">
     64    <part name="TerminateRequestBody" type="xsd1:terminateRequestType"/>
     65  </message>
     66
     67  <message name="TerminateResponseMessage">
     68    <part name="TerminateResponseBody" type="xsd1:terminateResponseType"/>
     69  </message>
     70
     71  <message name="FaultMessage">
     72    <part name="FaultBody" type="xsd1:faultType"/>
     73  </message>
     74
     75  <portType name="feddPortType">
     76    <operation name="RequestAccess">
     77      <documentation>
     78        Request access to a testbed.  The request includes the various
     79        resources needed (loosely), the identity of the requester, access
     80        credentials andscheduling information.  A successful response includes
     81        enough information for the federation system to access the testbed and
     82        actually request resources.
     83      </documentation>
     84      <input message="tns:RequestAccessRequestMessage"/>
     85      <output message="tns:RequestAccessResponseMessage"/>
     86      <fault name="RequestAccessFeddFault" message="tns:FaultMessage"/>
     87    </operation>
     88    <operation name="ReleaseAccess">
     89      <documentation>
     90        Release an allocation of access to a testbed. This informs the testbed
     91        that it is no longer necessary to allow the access mthods negotiated by
     92        a RequestAccess cal.
     93      </documentation>
     94      <input message="tns:ReleaseAccessRequestMessage"/>
     95      <output message="tns:ReleaseAccessResponseMessage"/>
     96      <fault name="ReleaseAccessFeddFault" message="tns:FaultMessage"/>
     97    </operation>
     98    <operation name="Create">
     99      <documentation>
     100        A request to create a federated experiment from the included
     101        description.  Credentials and access information is also provided.  On
     102        success a logical description of the experiment is returned as well as
     103        the information about federated testbeds needed to access local
     104        services.
     105      </documentation>
     106      <input message="tns:CreateRequestMessage"/>
     107      <output message="tns:CreateResponseMessage"/>
     108      <fault name="CreateFeddFault" message="tns:FaultMessage"/>
     109    </operation>
     110    <operation name="Vtopo">
     111      <documentation>
     112        A request for the virtual topology of the experiment.  Requesters with
     113        different access rights may receive different information.
     114      </documentation>
     115      <input message="tns:VtopoRequestMessage"/>
     116      <output message="tns:VtopoResponseMessage"/>
     117      <fault name="VtopoFeddFault" message="tns:FaultMessage"/>
     118    </operation>
     119    <operation name="Vis">
     120      <documentation>
     121        A request for the visualization of the experiment.  This is really a
     122        legacy interface for visual tools that cannot generate their own
     123        visualization.  Requesters with different access rights may receive
     124        different information.
     125      </documentation>
     126      <input message="tns:VisRequestMessage"/>
     127      <output message="tns:VisResponseMessage"/>
     128      <fault name="VisFeddFault" message="tns:FaultMessage"/>
     129    </operation>
     130    <operation name="Info">
     131      <documentation>
     132        A one-stop request for meta-data on the experiment.  Includes all the
     133        info from a Vtopo and a Vis request.
     134      </documentation>
     135      <input message="tns:InfoRequestMessage"/>
     136      <output message="tns:InfoResponseMessage"/>
     137      <fault name="InfoFeddFault" message="tns:FaultMessage"/>
     138    </operation>
     139    <operation name="Terminate">
     140      <documentation>
     141        Stop this experiment and deallocate its resources.
     142      </documentation>
     143      <input message="tns:TerminateRequestMessage"/>
     144      <output message="tns:TerminateResponseMessage"/>
     145      <fault name="TerminateFeddFault" message="tns:FaultMessage"/>
     146    </operation>
     147  </portType>
     148
     149  <binding name="feddBinding" type="tns:feddPortType">
     150      <documentation>
     151        These are really very straight ahead SOAP RPC bindings.  They're 1.1
     152        SOAP and not much outside the defaults.  No interesting header packing
     153        or fault configuration yet.
     154      </documentation>
     155    <soap:binding style="rpc"
     156      transport="http://schemas.xmlsoap.org/soap/http"/>
     157      <operation name="RequestAccess">
     158        <documentation>
     159          The bindings of this operation are straightforward SOAP RPC 1.1.
     160        </documentation>
     161        <soap:operation soapAction="RequestAccess"/>
     162        <input>
     163          <soap:body use="encoded" parts="tns:RequestAccessRequestBody"
     164            namespace="http://www.isi.edu/faber/fedd.wsdl"
     165            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     166        </input>
     167        <output>
     168          <soap:body use="encoded" parts="tns:RequestAccessResponseBody"
     169            namespace="http://www.isi.edu/faber/fedd.wsdl"
     170            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     171        </output>
     172        <fault name="RequestAccessFeddFault">
     173          <soap:fault use="encoded"  name="tns:FeddFault"
     174            namespace="http://www.isi.edu/faber/fedd.wsdl"
     175            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     176        </fault>
     177      </operation>
     178      <operation name="ReleaseAccess">
     179        <documentation>
     180          The bindings of this operation are straightforward SOAP RPC 1.1.
     181        </documentation>
     182        <soap:operation soapAction="ReleaseAccess"/>
     183        <input>
     184          <soap:body use="encoded" parts="tns:ReleaseAccessRequestBody"
     185            namespace="http://www.isi.edu/faber/fedd.wsdl"
     186            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     187        </input>
     188        <output>
     189          <soap:body use="encoded" parts="tns:ReleaseAccessResponseBody"
     190            namespace="http://www.isi.edu/faber/fedd.wsdl"
     191            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     192        </output>
     193        <fault name="ReleaseAccessFeddFault">
     194          <soap:fault use="encoded"  name="tns:FeddFault"
     195            namespace="http://www.isi.edu/faber/fedd.wsdl"
     196            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     197        </fault>
     198      </operation>
     199      <operation name="Create">
     200        <documentation>
     201          The bindings of this operation are straightforward SOAP RPC 1.1.
     202        </documentation>
     203        <soap:operation soapAction="Create"/>
     204        <input>
     205          <soap:body use="encoded" parts="tns:CreateRequestBody"
     206            namespace="http://www.isi.edu/faber/fedd.wsdl"
     207            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     208        </input>
     209        <output>
     210          <soap:body use="encoded" parts="tns:CreateResponseBody"
     211            namespace="http://www.isi.edu/faber/fedd.wsdl"
     212            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     213        </output>
     214        <fault name="CreateFeddFault">
     215          <soap:fault use="encoded"  name="tns:FeddFault"
     216            namespace="http://www.isi.edu/faber/fedd.wsdl"
     217            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     218        </fault>
     219      </operation>
     220      <operation name="Vtopo">
     221        <documentation>
     222          The bindings of this operation are straightforward SOAP RPC 1.1.
     223        </documentation>
     224        <soap:operation soapAction="Vtopo"/>
     225        <input>
     226          <soap:body use="encoded" parts="tns:VtopoRequestBody"
     227            namespace="http://www.isi.edu/faber/fedd.wsdl"
     228            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     229        </input>
     230        <output>
     231          <soap:body use="encoded" parts="tns:VtopoResponseBody"
     232            namespace="http://www.isi.edu/faber/fedd.wsdl"
     233            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     234        </output>
     235        <fault name="VtopoFeddFault">
     236          <soap:fault use="encoded"  name="tns:FeddFault"
     237            namespace="http://www.isi.edu/faber/fedd.wsdl"
     238            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     239        </fault>
     240      </operation>
     241
     242      <operation name="Vis">
     243        <documentation>
     244          The bindings of this operation are straightforward SOAP RPC 1.1.
     245        </documentation>
     246        <soap:operation soapAction="Vis"/>
     247        <input>
     248          <soap:body use="encoded" parts="tns:VisRequestBody"
     249            namespace="http://www.isi.edu/faber/fedd.wsdl"
     250            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     251        </input>
     252        <output>
     253          <soap:body use="encoded" parts="tns:VisResponseBody"
     254            namespace="http://www.isi.edu/faber/fedd.wsdl"
     255            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     256        </output>
     257        <fault name="VisFeddFault">
     258          <soap:fault use="encoded"  name="tns:FeddFault"
     259            namespace="http://www.isi.edu/faber/fedd.wsdl"
     260            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     261        </fault>
     262      </operation>
     263      <operation name="Info">
     264        <documentation>
     265          The bindings of this operation are straightforward SOAP RPC 1.1.
     266        </documentation>
     267        <soap:operation soapAction="Info"/>
     268        <input>
     269          <soap:body use="encoded" parts="tns:InfoRequestBody"
     270            namespace="http://www.isi.edu/faber/fedd.wsdl"
     271            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     272        </input>
     273        <output>
     274          <soap:body use="encoded" parts="tns:InfoResponseBody"
     275            namespace="http://www.isi.edu/faber/fedd.wsdl"
     276            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     277        </output>
     278        <fault name="InfoFeddFault">
     279          <soap:fault use="encoded"  name="tns:FeddFault"
     280            namespace="http://www.isi.edu/faber/fedd.wsdl"
     281            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     282        </fault>
     283      </operation>
     284      <operation name="Terminate">
     285        <documentation>
     286          The bindings of this operation are straightforward SOAP RPC 1.1.
     287        </documentation>
     288        <soap:operation soapAction="Terminate"/>
     289        <input>
     290          <soap:body use="encoded" parts="tns:TerminateRequestBody"
     291            namespace="http://www.isi.edu/faber/fedd.wsdl"
     292            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     293        </input>
     294        <output>
     295          <soap:body use="encoded" parts="tns:TerminateResponseBody"
     296            namespace="http://www.isi.edu/faber/fedd.wsdl"
     297            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     298        </output>
     299        <fault name="TerminateFeddFault">
     300          <soap:fault use="encoded"  name="tns:FeddFault"
     301            namespace="http://www.isi.edu/faber/fedd.wsdl"
     302            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     303        </fault>
     304      </operation>
     305    </binding>
     306
     307    <service name="feddService">
     308      <documentation>
     309        Fedd resource access service
     310      </documentation>
     311      <port name="feddPort" binding="tns:feddBinding">
     312        <soap:address location="http://www.isi.edu/faber/fedd"/>
     313      </port>
     314    </service>
    18315</definitions>
    19 

  • fedd/wsdl/fedd_internal.wsdl

    rf4cc4b7 r5858c72  
    22<definitions name="fedd_internal"
    33  targetNamespace="http://www.isi.edu/faber/fedd_internal.wsdl"
    4   xmlns:tns="http://www.isi.edu/faber/fedd_messages"
    5   xmlns:bns="http://www.isi.edu/faber/fedd_bindings"
     4  xmlns:tns="http://www.isi.edu/faber/fedd_internal.wsdl"
    65  xmlns:xsd1="http://www.isi.edu/faber/fedd_types"
    76  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    … …  
    1110    location="fedd_types.xsd"/>
    1211
    13   <import namespace="http://www.isi.edu/faber/fedd_internal_messages"
    14     location="fedd_internal_messages.wsdl"/>
     12  <!--
     13  The message definitions are all simple embeddings of one of the types
     14  from fedd_types.xsd
     15  -->
    1516
    16   <import namespace="http://www.isi.edu/faber/fedd_internal_bindings"
    17     location="fedd_internal_bindings.wsdl"/>
     17  <message name="FaultMessage">
     18    <part name="FaultBody" type="xsd1:faultType"/>
     19  </message>
     20
     21  <message name="AllocateProjectRequestMessage">
     22    <part name="AllocateProjectRequestBody" type="xsd1:projectAllocType"/>
     23  </message>
     24
     25  <message name="AllocateProjectResponseMessage">
     26    <part name="AllocateProjectResponseBody" type="xsd1:projectAllocType"/>
     27  </message>
     28
     29  <message name="StaticProjectRequestMessage">
     30    <part name="StaticProjectRequestBody" type="xsd1:projectAllocType"/>
     31  </message>
     32
     33  <message name="StaticProjectResponseMessage">
     34    <part name="StaticProjectResponseBody" type="xsd1:projectAllocType"/>
     35  </message>
     36
     37  <message name="ReleaseProjectRequestMessage">
     38    <part name="ReleaseProjectRequestBody" type="xsd1:projectAllocType"/>
     39  </message>
     40
     41  <message name="ReleaseProjectResponseMessage">
     42    <part name="ReleaseProjectResponseBody" type="xsd1:projectAllocType"/>
     43  </message>
     44
     45  <message name="Ns2SplitRequestMessage">
     46    <part name="Ns2SplitRequestBody" type="xsd1:ns2SplitRequestType"/>
     47  </message>
     48
     49  <message name="Ns2SplitResponseMessage">
     50    <part name="Ns2SplitResponseBody" type="xsd1:ns2SplitResponseType"/>
     51  </message>
     52
     53  <portType name="feddInternalPortType">
     54    <operation name="AllocateProject">
     55      <documentation>
     56        This internal interface allows the part of a fedd running on a machine
     57        other than the boss node of the emulab in question to request creation
     58        of a dynamic project on the boss node.
     59      </documentation>
     60      <input message="tns:AllocateProjectRequestMessage"/>
     61      <output message="tns:AllocateProjectResponseMessage"/>
     62      <fault name="AllocateFault" message="tns:FaultMessage"/>
     63    </operation>
     64    <operation name="StaticProject">
     65      <documentation>
     66        This internal interface allows the part of a fedd running on a machine
     67        other than the boss node of the emulab in question to request
     68        modification of a static project.  For example keys can be added or
     69        node access granted.
     70      </documentation>
     71      <input message="tns:StaticProjectRequestMessage"/>
     72      <output message="tns:StaticProjectResponseMessage"/>
     73      <fault name="StaticFault" message="tns:FaultMessage"/>
     74    </operation>
     75    <operation name="ReleaseProject">
     76      <documentation>
     77        This internal interface allows the part of a fedd running on a machine
     78        other than the boss node of the emulab in question to release resources
     79        allocated to either a static or dynamic project.
     80      </documentation>
     81      <input message="tns:ReleaseProjectRequestMessage"/>
     82      <output message="tns:ReleaseProjectResponseMessage"/>
     83      <fault name="ReleaseFault" message="tns:FaultMessage"/>
     84    </operation>
     85    <operation name="Ns2Split">
     86      <documentation>
     87        This allows a fedd that does not have direct access to the modified ns
     88        parser that splits a CEDL description into federation data to access
     89        that functionality remotely.
     90      </documentation>
     91      <input message="tns:Ns2SplitRequestMessage"/>
     92      <output message="tns:Ns2SplitResponseMessage"/>
     93      <fault name="Ns2SplitFault" message="tns:FaultMessage"/>
     94    </operation>
     95  </portType>
     96
     97  <binding name="feddInternalBinding" type="tns:feddInternalPortType">
     98      <documentation>
     99        These are really very straight ahead SOAP RPC bindings.  They're 1.1
     100        SOAP and not much outside the defaults.  No interesting header packing
     101        or fault configuration yet.
     102      </documentation>
     103    <soap:binding style="rpc"
     104      transport="http://schemas.xmlsoap.org/soap/http"/>
     105      <operation name="AllocateProject">
     106        <documentation>
     107          The bindings of this operation are straightforward SOAP RPC 1.1.
     108        </documentation>
     109        <soap:operation soapAction="AllocateProject"/>
     110        <input>
     111          <soap:body use="encoded" parts="tns:AllocateProjectRequestBody"
     112            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     113            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     114        </input>
     115        <output>
     116          <soap:body use="encoded" parts="tns:AllocateProjectResponseBody"
     117            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     118            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     119        </output>
     120        <fault name="AllocateFault">
     121          <soap:fault use="encoded"  name="tns:AllocateProjectFault"
     122            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     123            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     124        </fault>
     125      </operation>
     126      <operation name="StaticProject">
     127        <documentation>
     128          The bindings of this operation are straightforward SOAP RPC 1.1.
     129        </documentation>
     130        <soap:operation soapAction="StaticProject"/>
     131        <input>
     132          <soap:body use="encoded" parts="tns:StaticProjectRequestBody"
     133            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     134            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     135        </input>
     136        <output>
     137          <soap:body use="encoded" parts="tns:StaticProjectResponseBody"
     138            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     139            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     140        </output>
     141        <fault name="StaticFault">
     142          <soap:fault use="encoded"  name="tns:StaticProjectFault"
     143            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     144            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     145        </fault>
     146      </operation>
     147      <operation name="ReleaseProject">
     148        <documentation>
     149          The bindings of this operation are straightforward SOAP RPC 1.1.
     150        </documentation>
     151        <soap:operation soapAction="ReleaseProject"/>
     152        <input>
     153          <soap:body use="encoded" parts="tns:ReleaseProjectRequestBody"
     154            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     155            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     156        </input>
     157        <output>
     158          <soap:body use="encoded" parts="tns:ReleaseProjectResponseBody"
     159            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     160            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     161        </output>
     162        <fault name="ReleaseFault">
     163          <soap:fault use="encoded"  name="tns:ReleaseProjectFault"
     164            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     165            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     166        </fault>
     167      </operation>
     168      <operation name="Ns2Split">
     169        <documentation>
     170          The bindings of this operation are straightforward SOAP RPC 1.1.
     171        </documentation>
     172        <soap:operation soapAction="Ns2Split"/>
     173        <input>
     174          <soap:body use="encoded" parts="tns:Ns2SplitRequestBody"
     175            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     176            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     177        </input>
     178        <output>
     179          <soap:body use="encoded" parts="tns:Ns2SplitResponseBody"
     180            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     181            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     182        </output>
     183        <fault name="Ns2SplitFault">
     184          <soap:fault use="encoded"  name="tns:Ns2SplitFault"
     185            namespace="http://www.isi.edu/faber/fedd_internal.wsdl"
     186            encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
     187        </fault>
     188      </operation>
     189    </binding>
     190
     191    <service name="feddInternalService">
     192      <documentation>
     193        Fedd resource access service
     194      </documentation>
     195      <port name="fedd_internal_port" binding="tns:feddInternalBinding">
     196        <soap:address location="http://www.isi.edu/faber/fedd_internal"/>
     197      </port>
     198    </service>
    18199</definitions>
    19 
Note: See TracChangeset for help on using the changeset viewer.