- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 21 Jan 2009 14:44:35 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463
Summary: Attaching Policy to WS-Mex GetMetadata
Product: WS-Resource Access
Version: PR
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: MetadataExchange
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: katy_warr@uk.ibm.com
We should consider clarifying or recommending how policy should be associated
with a WS-MetadataExchange GetMetadata request. ('Policy' might be existing
policies such as WS-SecurityPolicy or potential new assertions, as described in
issue 6406 here: http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406).
A GetMetadata operation's policy cannot be attached within the Web service
endpoint's WSDL because:
In order for a client to establish the WS-Mex GetMetadata policy, it would need
to issue a GetMetadata(WSDL) request at the web service endpoint...but in order
to issue a GetMetadata request at the endpoint it would need to establish the
WS-Mex GetMetadata policy...
The issue here is: what is the correct way to bootstrap the bootstrap (without
entering an infinite loop)?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Received on Wednesday, 21 January 2009 14:44:46 UTC