OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-policy message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-policy] Issue 15 -- WSDL URIs for addressing interface components


Mike:
Here are a couple of examples of how the WSDL URIs may be used.  Assume 
we are writing a function that locates a particular
interface component for a particular instance of a binding. 
Assume the WSDL definitions file is at 
http:/www.wsdlDefinitions.mydefinition

Such a function could be written with the following signature.
locateMessageForBinding(bindingElementName(bindingName=" ...",         
http:/www.wsdlDefinitions/mydefinition#wsdl11.message(messageName))

If the interface was WSDL 2.0 we may want to define something like
locateMessageForBinding(bindingElementName(bindingName=" ...",         
http:/www.wsdlDefinitions/mydefinition#wsdl.interfaceMessageReference(interfaceName/operationName/messageName))
All the best, Ashok


Mike Edwards wrote:
>
> Ashok,
>
> Thanks for writing this up.
>
> Could you give a couple of examples of this style of addressing being 
> used in the expressions used
> to attach policies using the external attachment mechanism?  I'm not 
> sure that I see how it fits.
>
>
> Yours,  Mike.
>
> Strategist - Emerging Technologies, SCA & SDO.
> Co Chair OASIS SCA Assembly TC.
> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
> Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
> Email:  mike_edwards@uk.ibm.com
>
>
> *ashok malhotra <ashok.malhotra@oracle.com>*
>
> 09/06/2008 22:37
> Please respond to
> ashok.malhotra@oracle.com
>
>
> 	
> To
> 	OASIS Policy <sca-policy@lists.oasis-open.org>
> cc
> 	
> Subject
> 	[sca-policy] Issue 15 -- WSDL URIs for addressing interface components
>
>
>
> 	
>
>
>
>
>
> WSDL 2.0 defined URIs to address individual components in a WSDL
> definitions file.
> These URIs are defined in Appendix A.2 of http://www.w3.org/TR/wsdl20.
> Essentially, this Appendix defines fragment identifier that can be added
> as a suffix to the URI
> for a WSDL 2.0 file to identify individual interface components.
> For example, the fragId of a message reference is
> wsdl.interfaceMessageReference(interface/operation/message)
> where the information within the parenthesis is the name of the
> interface. the operation and the message.
>
> WS-Policy, recognizing the need for similar identifiers for WSDL 1.1,
> published http://www.w3.org/TR/wsdl11elementidentifiers
> which defines fragment identifiers for WSDL 1.1 interface elements along
> the same lines.
> For example the fragID for Binding Operation Input is
> |wsdl11.bindingOperation.input(||binding/operation||)
>
> I suggest we use these identifiers in External Policy Attachment as
> Domain Expressions to
> identify where policySets should be attached.
> |
> -- 
> All the best, Ashok
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>
>
> ------------------------------------------------------------------------
>
> /
> /
>
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with 
> number 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 
> 3AU/
>
>
>
>
>
>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]