wsrp message
[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
- From: Rich Thompson <richt2@us.ibm.com>
- To: wsrp@lists.oasis-open.org
- Date: Tue, 15 Aug 2006 10:22:04 -0400
Agreed, the original v2 service wsdl
had just a single service element with ports for both the v1 and v2 bindings.
People found that confusing and decided it would be cleaner to separate
the ports into version oriented service elemeents.
Rich
Richard Jacob <richard.jacob@de.ibm.com>
08/15/2006 09:35 AM
|
To
| Rich Thompson/Watson/IBM@IBMUS
|
cc
| wsrp@lists.oasis-open.org
|
Subject
| RE: [wsrp] Re: [wsrp-comment] Issues
with wsrp_services.wsdl |
|
I remember the discussion.
But if this is one logical producer then why doesn't it simply define a
single service element with v1 and v2 ports (and binding references)? Isn't
that easier and even more kompatible?
A v1 consumer would pick up the service element and filter out the port
definitions it needs/understands.
In general I think producers could do whatever they want and consumers
need
to prepare for it.
But I would expect most v1 consumers to fail if they hit a wsdl with to
service definitions in it.
I find it quite a stretch to have two service definitions and saying that
they are logically the same (and even can exchange handles) where the
structure (wsdl) doesn't provide any means to tie those.
It seems to me that a single service element expresses the tie pretty
clean.
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
Rich Thompson
<richt2@us.ibm.co
m>
To
wsrp@lists.oasis-open.org
08/15/06 02:39 PM
cc
Subject
RE: [wsrp]
Re: [wsrp-comment]
Issues with
wsrp_services.wsdl
We had this discussion earlier. The outcome was that we expect most
Producers would offer separate wsdls for v1 and v2 services, but that it
was legal wsdl for them to offer both in a single "service" wsdl.
The
following comment was added to provide guidance to those making that choice
(& the decision was to include both so that the comment makes sense):
"<!-- Since this wsdl includes both v1 and v2 service
elements, theConsumer will expect resources (e.g. registrationHandle,
registrationState, etc) cancross the service boundaries -->"
The point is that the Producer with a combined wsdl is publishing itself
as
a single logical service with multiple entry points. Separate wsdls would
be separate logical services with no implied connection between them.
Rich
Richard Jacob
<richard.jacob@de.ibm.c
om>
To
"Subbu Allamaraju" <subbu@bea.com>
08/15/2006 05:07 AM
cc
"Nathan Lipke" <nlipke@bea.com>,
Rich
Thompson/Watson/IBM@IBMUS,
wsrp@lists.oasis-open.org
Subject
RE: [wsrp] Re: [wsrp-comment]
Issues with
wsrp_services.wsdl
One more comment on the WSDL.
Should our service wsdl contain both services or would we prefer one
service wsdl per version?
For backwards compatibility I would expect that most 1.0 consumers wouldn't
be able to filter out the 1.0 service if multiple services were present
in
the WSDL.
Although not normative and WSDL allows to have more than one service
element in it, it could be cleaner to seperate them anyway?
Do we intend to have a logical tie between the 1.0 service and the 2.0
service? I.e. can we exchange handles across the version specific bindings?
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
"Subbu
Allamaraju"
<subbu@bea.com>
To
Richard Jacob/Germany/IBM@IBMDE,
08/14/06 06:53 PM
"Nathan Lipke" <nlipke@bea.com>
cc
"Rich
Thompson"
<richt2@us.ibm.com>,
<wsrp@lists.oasis-open.org>
Subject
RE: [wsrp]
Re: [wsrp-comment]
Issues with
wsrp_services.wsdl
Just noticed that there is a minor problem with the binding names used
in
the V2 spec. The names used (e.g. WSRPv2ServiceDescription_Binding_SOAP)
don't match those specified in the v2 bindings file (which uses
WSRP_v2_ServiceDescription_Binding_SOAP).
The same is the case with portTypes.
Sec 15 of the spec should be fixed to use the same names.
Subbu
-----Original Message-----
From: Richard Jacob [mailto:richard.jacob@de.ibm.com]
Sent: Fri 8/11/2006 2:27 AM
To: Nathan Lipke
Cc: Rich Thompson; wsrp@lists.oasis-open.org
Subject: Re: [wsrp] Re: [wsrp-comment] Issues with wsrp_services.wsdl
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 v2definitionsto be used -->
<import
namespace="urn:oasis:names:tc:wsrp:v2:bind"
location="wsrp_v2_bindings.wsdl"/>
<!--
Since this wsdl includes both v1 and v2serviceelements, the Consumer will expect resources(e.g.registrationHandle, registrationState, etc) can cross theserviceboundaries -->
<import
namespace="urn:oasis:names:tc:wsrp:v1:wsdl"
location="wsrp_service.wsdl"/>
<!--
A service definition encapsulating the WSRPv2support 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.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]