You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commons-dev@ws.apache.org by "Eran Chinthaka (JIRA)" <ji...@apache.org> on 2006/06/13 11:08:30 UTC

[jira] Updated: (WSCOMMONS-42) Ability to add extensions to Neethi

     [ http://issues.apache.org/jira/browse/WSCOMMONS-42?page=all ]

Eran Chinthaka updated WSCOMMONS-42:
------------------------------------

    Attachment: patch.txt

> Ability to add extensions to Neethi
> -----------------------------------
>
>          Key: WSCOMMONS-42
>          URL: http://issues.apache.org/jira/browse/WSCOMMONS-42
>      Project: WS-Commons
>         Type: New Feature

>   Components: Policy
>     Reporter: Eran Chinthaka
>     Assignee: Eran Chinthaka
>  Attachments: patch.txt
>
> Current Neethi implementation seems lagging support to integrate other extensions. 
> Here is a proposal with a patch to implement it. 
> There are extensions which can process domain specific policies.
> When policy processor sees an unknown namespace, the extensions registered which can process that particular element. is handed over that element. The task of that extension is to process the given OMElement and return back an Assertions. In this way, other extensions like security, RM can be intergrated bettter with policy. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org