Hi David,
You said it at the end below:
1) QueryInterfaceWSDL returns "a WSDL that describes the interface"
(and NOT a specific WSDL endpoint identifier)
2) QueryInterfaceEndPoint - Client MUST use this to
discover the actual WSDL endpoint
OK?
Cheers,
- Ira McDonald
High North Inc
-----Original Message-----
From: HALL,DAVID (HP-Vancouver,ex1) [mailto:dhall at hp.com]
Sent: Tuesday, December 10, 2002 11:39 AM
To: 'ps at pwg.org'
Subject: PS> QueryInterfaceWSDL discussion
During today's meeting, we discussed the QueryInterfacWSDL method, and came
up with the following statement:
- For example, target devices could return a URL to the WSDL
that is hosted by the manufacturer, and not on the printer, or to the WSDL
that is configured by the administrator.
I don't think that this will actually work however. The WSDL typically has
a service binding within it, and this couldn't be returned generically - The
whole point of calling this method was to figure out what URL path to bind
to for the interface you are requesting.
<wsdl:service name="JobControlInterfaceService">
<wsdl:port name="org.pwg.psi.JobControlInterface"
binding="intf:org.pwg.psi.JobControlInterfaceSoapBinding">
<wsdlsoap:address
location="http://127.0.0.1/org.pwg.psi.JobControlInterface"/>
</wsdl:port>
</wsdl:service>
We could change the meaning of the method to be "retrieve a WSDL that
describes the interface" - but the client MUST use QueryInterfaceEndPoint to
get the end point to bind to...
Thoughts?
Dave