Clarifications on multiple portTypes

["Vambenepe, William N" <vbp@hp.com>]

Hi all,

Since I didn't manage to convince the group that "portType copy/paste"
method should provide a way for the consumer of the WSDL doc to find the
Qnames of the portTypes implemented (which to me negates the value of
WSDL) I am trying to find a way to use WS-ResourceProperties in a way
that provides this information in accordance with our spec. Moving the
"copy-paste" stuff outside of WS-RP was one step in this direction. I
would like to hear comments from the group on the approach below.

My WSDL looks like:

<definition targetnamespace="http://myNS.com/";
   xmlns:tns="http://myNS.com/";
   xmlns:foo="http://foo.com";
   xmlns:bar="http://bar.com";
 
xmlns:wsrp="http://docs.oasis-open.org/wsrf/2005/03/wsrf-WS-ResourceProp
erties-1.2-draft-06.wsdl">

   <import namespace="http://foo.com"/>
   <import namespace="http://bar.com"/>
   <import
namespace="http://docs.oasis-open.org/wsrf/2005/03/wsrf-WS-ResourcePrope
rties-1.2-draft-06.wsdl"/>

   <binding name="bindingA" type="foo:A">
      ...
   </binding>

   <binding name="bindingB" type="bar:B">
      ...
   </binding>

   <binding name="bindingWSRP" type="wsrp:GetResourcePropertyDocument">
      ...
   </binding>

   <service name="myService">

      <port name="PortA" binding="tns:bindingA">
         <soap:address location="http://myServer/myEndpoint"/>
      </port>
      <port name="PortB" binding="tns:bindingB">
         <soap:address location="http://myServer/myEndpoint"/>
      </port>
      <port name="PortWSRP" binding="tns:bindingWSRP">
         <soap:address location="http://myServer/myEndpoint"/>
      </port>
   </service>

</definition>

Questions to the group:

- Is it ok to assume that the fact that portA and portB are part of the
same service implies that they are used to access the same WS-Resource?
Is this something that needs to be added to the App notes?

- If each of the portTypes (foo:A and bar:B) have resource properties
documents defined (respectively foo:resPropA and bar:resPropB) is it ok
to assume that by invoking GetResourcePropertyDocument I will get back a
document that contains the properties defined in both foo:ResPropA and
bar:resPropB)? Should we make this clear in the spec?

- How do we address the case where resource properties are defined but
no operation is defined by the associated portType? Do we have a binding
for an empty portType and a port for this service?

Once we answer these questions (and any other that might be raised by
this example WSDL) I suggest that the primer include an example like
this one for users who do not want to be forced to use the copy/paste
method for aggregating portTypes.

Regards,

William