[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp] Re: [wsrp-comment] Issues with wsrp_services.wsdl
I agree with Richard. As a style it would be nice to follow the same style, but in any case, the WSDL is non-normative. Subbu Nathan E Lipke wrote: > Right using the binding is the best way. Still I see no reason not to > keep it the same as v1. > > Nate > > Richard Jacob wrote: >> just to clarify and split hairs: >> >> The only reliable way for a consumer to determine the correct port is the >> binding attribute on the wsdl:port element. It is not the name >> attribute of >> the port. The name attribute can be changed in any arbitrary way as >> well as >> the service name attribute. >> >> Mit freundlichen Gruessen / best regards, >> >> Richard Jacob >> ______________________________________________________ >> IBM Lab Boeblingen, Germany >> Dept.8288, WebSphere Portal Server Development >> WSRP Technical Lead >> WSRP Standardization >> Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888 >> Email: mailto:richard.jacob@de.ibm.com >> >> >> >> Nathan E >> Lipke >> <nlipke@bea.com> >> >> To 08/10/06 10:04 PM Rich Thompson >> <richt2@us.ibm.com> >> >> cc >> wsrp@lists.oasis-open.org >> >> Subject [wsrp] Re: >> [wsrp-comment] Issues with >> wsrp_services.wsdl >> >> >> >> >> >> >> >> >> >> >> Yes its public review comment. >> >> Rich Thompson wrote: >> >> While I don't have a problem with the rework suggested, it is a bug >> if v1 Consumers are expecting all Producer to use the same name for >> their service elements as this is not required either by WSDL or >> WSRP. The implementation should look at either the binding or >> portType names to ensure compatibility (defined by the TC and >> therefore constant). >> >> By the way; are you intending this as a public review comment such >> that the changes actually appear in what becomes the v2 package of >> files? >> >> Rich >> >> >> Nathan E Lipke >> <nlipke@bea.com> >> >> >> 08/10/2006 01:07 >> PM To >> >> wsrp-interfaces@lists.oasis >> >> -open.org >> >> cc >> >> >> Subject >> [wsrp-interfaces] Issues >> with >> wsrp_services.wsdl >> >> >> >> >> >> >> >> >> >> >> >> >> I've found a couple of issues of with the wsrp_services.wsdl posted >> on oasis. >> 1st the service and port names for were changed from v1 >> This may break v1 consumers looking for specific >> service >> and port names >> The targetNamespace is v2 for all ports and services >> Again may cause issues v1 consumers >> I would like to propose keeping the v1 >> wsrp_services.wsdl >> as it was in v1 and having the v2 wsdl import the v1 >> wsdl. >> >> I attached samples of this (Note: wsrp_service.wsdl is >> version #4 (2003-04-17) from the Oasis site). >> >> Thanks, >> >> Nate >> >> _______________________________________________________________________ >> >> Notice: This email message, together with any >> attachments, may contain >> information of BEA Systems, Inc., its subsidiaries >> and affiliated >> entities, that may be confidential, proprietary, >> copyrighted and/or >> legally privileged, and is intended solely for the >> use of >> the individual >> or entity named in this message. If you are not the >> intended recipient, >> and have received this message in error, please >> immediately return this >> by email and then delete it. >> <?xml version="1.0" encoding="UTF-8"?> >> <wsdl:definitions >> targetNamespace="urn:oasis:names:tc:wsrp:v2:wsdl" >> >> xmlns:v2bind="urn:oasis:names:tc:wsrp:v2:bind" >> >> xmlns:v1bind="urn:oasis:names:tc:wsrp:v1:bind" >> >> >> xmlns="http://schemas.xmlsoap.org/wsdl/"; >> >> xmlns:wsdl= >> "http://schemas.xmlsoap.org/wsdl/"; >> xmlns:soap= >> "http://schemas.xmlsoap.org/wsdl/soap/";> >> >> <!-- The following causes the required WSRP v2 >> definitions to be used --> >> <import namespace="urn:oasis:names:tc:wsrp:v2:bind" >> location="wsrp_v2_bindings.wsdl"/> >> >> <!-- Since this wsdl includes both v1 and v2 service >> elements, the Consumer will expect resources >> (e.g. >> registrationHandle, registrationState, etc) can >> cross the >> service boundaries --> >> <import namespace="urn:oasis:names:tc:wsrp:v1:wsdl" >> location="wsrp_service.wsdl"/> >> >> >> <!-- A service definition encapsulating the WSRP v2 >> support of this Producer --> >> <wsdl:service name="WSRP_v2_Service"> >> <wsdl:port >> binding="v2bind:WSRP_v2_Markup_Binding_SOAP" >> name="WSRP_v2_Markup_Service"> >> <soap:address location= >> "http://my.service:8082/WSRPService"/> >> </wsdl:port> >> <wsdl:port >> >> binding="v2bind:WSRP_v2_ServiceDescription_Binding_SOAP" >> name="WSRP_v2_ServiceDescription_Service"> >> <soap:address location= >> "http://my.service:8082/WSRPService"/> >> </wsdl:port> >> <wsdl:port >> binding="v2bind:WSRP_v2_Registration_Binding_SOAP" >> name="WSRP_v2_Registration_Service"> >> <soap:address location= >> "http://my.service:8082/WSRPService"/> >> </wsdl:port> >> <wsdl:port >> binding="v2bind:WSRP_v2_PortletManagement_Binding_SOAP" >> name="WSRP_v2_PortletManagement_Service"> >> <soap:address location= >> "http://my.service:8082/WSRPService"/> >> </wsdl:port> >> </wsdl:service> >> </wsdl:definitions> >> <?xml version="1.0" encoding="UTF-8"?> >> <wsdl:definitions >> targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl" >> >> xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind" >> >> >> xmlns="http://schemas.xmlsoap.org/wsdl/"; >> >> xmlns:wsdl= >> "http://schemas.xmlsoap.org/wsdl/"; >> xmlns:soap= >> "http://schemas.xmlsoap.org/wsdl/soap/";> >> >> <import namespace="urn:oasis:names:tc:wsrp:v1:bind" >> location="wsrp_v1_bindings.wsdl"/> >> >> <wsdl:service name="WSRPService"> >> <wsdl:port >> binding="bind:WSRP_v1_Markup_Binding_SOAP" >> name="WSRPBaseService"> >> <soap:address location= >> "http://my.service:8080/WSRPService"/> >> </wsdl:port> >> <wsdl:port >> binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP" >> name="WSRPServiceDescriptionService"> >> <soap:address location= >> "http://my.service:8080/WSRPService"/> >> </wsdl:port> >> <wsdl:port >> binding="bind:WSRP_v1_Registration_Binding_SOAP" >> name="WSRPRegistrationService"> >> <soap:address location= >> "http://my.service:8080/WSRPService"/> >> </wsdl:port> >> <wsdl:port >> binding="bind:WSRP_v1_PortletManagement_Binding_SOAP" >> name="WSRPPortletManagementService"> >> <soap:address location= >> "http://my.service:8080/WSRPService"/> >> </wsdl:port> >> </wsdl:service> >> </wsdl:definitions> >> >> _______________________________________________________________________ >> Notice: This email message, together with any attachments, may contain >> information of BEA Systems, Inc., its subsidiaries and affiliated >> entities, that may be confidential, proprietary, copyrighted and/or >> legally privileged, and is intended solely for the use of the individual >> or entity named in this message. If you are not the intended recipient, >> and have received this message in error, please immediately return this >> by email and then delete it. >> >> >> > _______________________________________________________________________ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]