Hi Manjula,

Implement Policy Intersection support is can be done. But when remove domain specific assertion form Neethi/C it will make dependencies for Axis2/C. For an example if we bring security builders to Rampart/C, Axis2/C engine will depend on Rampart/C. But there are some solution to do this.Can use a mapping mechanism using a hash map to do this ?

Regards,
Manoj
Manjula Peiris wrote:
Hi Manoj,

You need to implement two tasks.

1. Implement Policy Intersection support as described in Web services
policy spec 1.2 section 4.4
 - Actually this may be similar to policy merge support implemented in
Neethi/C . Please refer ,
https://svn.apache.org/repos/asf/webservices/axis2/trunk/c/neethi/src/engine.c

for more information.

2. Removing domain specific assertion processing from Neethi/C
- Currently domain specific assertions are handled inside Neethi/C. For
example Security Policy assertions are handled from builders inside
secpolicy. But for a clean design these should be handled from
Rampart/C. You need to come up with a solution where these assertion
processing handled from Rampart/C, but the Axis2/C engine still not
depend on Rampart/C.

You can go through the current implementation and understand the
context. If you have any questions please ask in this list.

Thanks,
-Manjula.



On Wed, 2008-03-26 at 13:23 +0530, Manoj wrote:
Hi all,

I am an undergraduate of Information Technology from University of Moratuwa and I saw the proposal "Improvements to Axis2/C Neethi". I read some of the things on this topic. I'm very interested in WS-Policy. So I would like to do this project. Can I have some more details of this project?

Regards
Manoj







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to