Oops forget to put the prefix, seems I have been too far away
---------- Forwarded message ----------
From: Srinath Perera <[EMAIL PROTECTED]>
Date: Feb 13, 2006 5:29 PM
Subject: State of WS-Policy?
To: "[email protected]" <[email protected]>
Hi All;
I want to ask the state of our policy implementation, and how much the
policy descriptions are bound to modules?
I saw from the code, if there are modules engaged, they are printed
out in WSDL as policy, do we support other side, engaging and
configure the
modules according to the WS-Policy information given in Axis2 configuration.
I am more interested in having the policy support in the client side,
and I believe it should be WSDL based. Have we done any work on it? If
not I would like to try to do something on the enabling them on the
dynamic client interface (give a wsdl and configure the
ServiceCleint/OperationClient) as a start
I wrote few thoughts and a possible implementation down, I think most
of it is already done. I want to tie the loose threads and use it and
to fix what ever I can. Please comment.
Thanks
Srinath
WS-Policy and Axis2 Modules are kind of parallel, I would view them as
one is abstract representation and other is implementation of the
representation. To build a policy model for Axis2 we need to describe
two scenarios
1) Build a Service, engage Modules and then create a WSDL description.
This is the most natural scenario for the Server side
2) Given a WSDL, extract the Policy and create a Service with modules engaged
The main work we have to do is
1) Provide a mapping from a given type of policy to a specific module,
then hand over handling that policy to module
2) Define the parameter conversion to and from the Policy, we have two options
a) We can define a mapping from policy to the our parameters
in the modules
b) We can use policy segments inside the service.xml file, for
an example for security module
Possible Implementation
=======================
1) Every module register a name space of the policy it can handle
2) If we start from Axis2 configuration Modules at engagement receive
the policy directly or via the service. The Policy could be Axis2
parameters or Policy xml segment. Following is example of policy
segment in engagement.
<service name="SecureService">
<engage name="">
<wsp:Policy>
...............
<sp:SignedSupportingTokens>
<wsp:Policy>
<sp:UsernameToken
sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Once";
/>
</wsp:Policy>
</sp:SignedSupportingTokens>
..........
</wsp:Policy>
</enagege>
</service>
3) When a WSDL is found with policy included, a module is called
based on the #1 mapping, and module is able to process the policy and
configure and engage himself
--
============================
Srinath Perera:
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
