Hi Anish,
Anish Karmarkar wrote:
49AF2D00.7060701@oracle.com" type="cite">1) In
section 3.1, bullet 3.1 (for service) says:
"... and references a wsdl:service element, then use the URI indicated
by each contained wsdl:port element"
In section 3.1, bullet 3 (for reference) says:
"If the @wsdlElement attribute is present and references a wsdl:service
element, use the URI indicated by any contained wsdl:port element that
satisfies runtime policies and constraints"
Any particular reason runtime policy and constraints are important for
reference but not for service?
We also say in the explanation of @wsdlElement that only those ports in
the WSDL service element that have equivalent portType are made
available.
I updated the wording on the (for service) section.
49AF2D00.7060701@oracle.com" type="cite">
2) We don't require that when endpointReference and @wsdlElement are
both used the wsdlElement MUST reference only a WSDL binding. If this
is true when @URI is specified, it should be true for endpointReference
as well. Both are a way to specify uris.
We
do have precisely the constraint you state here that we don't have:
"When this element is present along with the @wsdlElement attribute on
the parent element, the @wsdlElement attribute value MUST be of the
‘Binding’ form as specified above"
49AF2D00.7060701@oracle.com" type="cite">As a
side, an EPR can contain WSDL metadata. What happens if the EPR points
to a WSDL binding in its metadata section. Can it be different from the
one pointed to by @wsdlElement? I would like to suggest that it be a
"compatible super/subset".
Wow. The insanity. How about we leave it undefined?
49AF2D00.7060701@oracle.com" type="cite">
3) For reference (in bullet 5) it says:
"Otherwise, the URI for the reference is determined by the binding it
is wired to, or by deployment"
Isn't it always determined by the binding it is wired to?
Is it an error if you have <binding.ws /> but no target
specified? If you haven't specified a target, then you can wire this
at deployment.
49AF2D00.7060701@oracle.com" type="cite">
4) A very minor editorial comment. It would nice if the algorithms for
service and ref were structured (wrt bullets) similarly.
I'm not sure what you mean by this. Perhaps we can discuss during the
call. At a guess, I moved the last "otherwise" into a fifth bullet
point.
Revised version attached.
49AF2D00.7060701@oracle.com" type="cite">
-Anish
--
Eric Johnson wrote:
Attached as revisions to CD02.
I did my best to capture many of the points raised in the calls in
which
we talked about this, but I suspect I missed something.
If you review before next call, and have comments, I'll do my best to
integrate those comments before then.
Please excuse the fact that OpenOffice completely mangled the table of
contents. If you don't update the TOC before saving, it sometimes gets
confused. No changes intended there.
-Eric.
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|