[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue - 152 - Proposal to Vote
Suppose that I have an implementation where the scheme is the only thing I would need to identify the endpoint. For example, using a SOAP router that is internally bound to the BPEL engine, all I would need to do is to indicate that I want to invoke the SOAP router. Since the current service-ref schema defines that there must be exactly one child element, I would have to invent an element with the proper namespace: <service-ref> <foo:dummy xmlns:foo="urn:my-soap-router"/> </service-ref> In this scenario, it would be more compact (and less redundant) to use the reference-scheme attribute instead and omit the child element: <service-ref reference-scheme="urn:my-soap-router"/> To support this, we would have to change the definition of the <service-ref> element to allow for zero or one child element. Just thinking out loud.. Any Thoughts? Kristofer -----Original Message----- From: Martin Chapman [mailto:martin.chapman@oracle.com] Sent: Tuesday, August 31, 2004 12:29 PM To: 'Ron Ten-Hove'; ygoland@bea.com Cc: 'Alex Yiu'; 'Francisco Curbera'; wsbpel@lists.oasis-open.org Subject: RE: [wsbpel] Issue - 152 - Proposal to Vote It is indeed possible to not have the reference-scheme attribute and have the scheme be recognized from the QName of the child element of the wrapper element. For example, a WS-Addressing wsa:EndpointReference could be the child element of the wrapper element, and it would be very clear from the wsa:EndpointReference element as to which addressing scheme is being used. But this is not always the case as explained below. Therefore, it makes sense to have the reference-scheme attribute and make it optional. WS-MD uses the WSDL 1.1 service element to reference a Web service by adding certain restrictions to the wsdl11:service element -- all port child elements of the service element MUST be alternate ways to get to the same Web service. This restriction is over and above of WSDL 1.1 allows/requires. It is certainly possible for someone to use WSDL 1.1 service element to reference a Web service but not have the restriction imposed by WS-MD. Since the same QName will be used as the child element of the addressing wrapper element (i.e., wsdl11:service), without a reference-scheme disambiguator it will not be clear as to which addressing scheme is being used. Martin. >-----Original Message----- >From: Ron Ten-Hove [mailto:Ronald.Ten-Hove@Sun.COM] >Sent: 27 August 2004 23:52 >To: ygoland@bea.com >Cc: Martin Chapman; Alex Yiu; Francisco Curbera; >wsbpel@lists.oasis-open.org >Subject: Re: [wsbpel] Issue - 152 - Proposal to Vote > > >Yaron, > >Yaron Y. Goland wrote: > >> Since service-ref is an attribute how can reference-scheme be an >> attribute of service-ref? Attributes in XML cannot have attributes. > >This is a typo / misunderstanding; service-ref is an element, with a >reference-scheme attribute. Service-ref serves as a "wrapper" for the >EPR, so it must be an element. > >> >> Furthermore there can never be an ambiguity about the >namespace of the >> EPR because the EPR root element MUST always declare what its >> namespace is, even if it's nothing. >> >> So I'm still unclear as to what role the service-ref plays. > >The namespace of the enclosed EPR may be insufficient to identify the >addressing scheme in use. For instance, WS-MD uses wsdl:endpoint >elements for EPRs, and it is conceivable that other addressing schemes >may follow the same approach (if only newer versions of WS-MD!). > >-Ron > > >To unsubscribe from this mailing list (and be removed from the >roster of the OASIS TC), go to >http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/lea ve_workgroup.php. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup. php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]