Venkata Krishnan wrote:
Hi,
I observe are some intents named 'soap', 'soap11', 'soap12'. I'd like to
know if these are supposed to be intents classified as 'mayProvide' for
binding.ws.
Just to refresh, 'mayProvide' intents are those that can be specified for a
binding / implementation and that needs no matching policySet. i.e. this is
typically a capability that the binding / implementation which could be
switched on with just the specification of the intent on the binding /
implementation.
Given this, I don't see any policySets defined for these intents. So, I'd
like to add these intent names to the bindingType definition for binding.ws.
Again, just to refresh, the bindingtype information is something that is
typically specified in the definitions.xml file and it contains a list of
intents that are inherently supported by the binding in question, either as
'mustProvide' or 'mayProvide'.
Can folks familiar with binding.ws please say if my understanding is on
track ? Thanks.
- Venkat
Just noticed this pending question now. My understanding is the same as
yours, the Web Service binding should declare the soap, soap/1.1 and
soap/1.2 intents using the @mayProvide attribute.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
