You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Angel Todorov (JIRA)" <ji...@apache.org> on 2007/05/13 23:44:15 UTC

[jira] Created: (RAMPART-40) implementation of the Xpath support

implementation of the Xpath support 
------------------------------------

                 Key: RAMPART-40
                 URL: https://issues.apache.org/jira/browse/RAMPART-40
             Project: Rampart
          Issue Type: New Feature
          Components: rampart-core, rampart-policy
    Affects Versions: 1.1, 1.2
         Environment: Apache Axis2 1.2,  Rampart-head , tomcat 5.5.23
            Reporter: Angel Todorov
             Fix For: 1.2
         Attachments: svn_diff.txt

This is the implementation  (SVN Diff attached) of XPath support - <SignedElements> , <EncryptedElements>. For now there are two ways to retrieve the namespace prefixes. To use a predefined list of declared namespaces , as Ruchith is doing with the Optimized message parts , or to recursively find all namespaces in the message (that is the default in the implementation).

Ruchith,

I think we can make some custom parameter in Rampart-config that will set the strategy to use regarding namespace prefixes. 

Thanks.

Regards,
Angel

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (RAMPART-40) implementation of the Xpath support

Posted by "Angel Todorov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Angel Todorov updated RAMPART-40:
---------------------------------

    Attachment: svn_diff.txt

> implementation of the Xpath support 
> ------------------------------------
>
>                 Key: RAMPART-40
>                 URL: https://issues.apache.org/jira/browse/RAMPART-40
>             Project: Rampart
>          Issue Type: New Feature
>          Components: rampart-core, rampart-policy
>    Affects Versions: 1.1, 1.2
>         Environment: Apache Axis2 1.2,  Rampart-head , tomcat 5.5.23
>            Reporter: Angel Todorov
>             Fix For: 1.2
>
>         Attachments: svn_diff.txt
>
>
> This is the implementation  (SVN Diff attached) of XPath support - <SignedElements> , <EncryptedElements>. For now there are two ways to retrieve the namespace prefixes. To use a predefined list of declared namespaces , as Ruchith is doing with the Optimized message parts , or to recursively find all namespaces in the message (that is the default in the implementation).
> Ruchith,
> I think we can make some custom parameter in Rampart-config that will set the strategy to use regarding namespace prefixes. 
> Thanks.
> Regards,
> Angel

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (RAMPART-40) implementation of the Xpath support

Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruchith Udayanga Fernando resolved RAMPART-40.
----------------------------------------------

    Resolution: Fixed

Fixed in the latest SVN

> implementation of the Xpath support 
> ------------------------------------
>
>                 Key: RAMPART-40
>                 URL: https://issues.apache.org/jira/browse/RAMPART-40
>             Project: Rampart
>          Issue Type: New Feature
>          Components: rampart-core, rampart-policy
>    Affects Versions: 1.1, 1.2
>         Environment: Apache Axis2 1.2,  Rampart-head , tomcat 5.5.23
>            Reporter: Angel Todorov
>             Fix For: 1.2
>
>         Attachments: policy_ut_xpath.xml, svn_diff.txt
>
>
> This is the implementation  (SVN Diff attached) of XPath support - <SignedElements> , <EncryptedElements>. For now there are two ways to retrieve the namespace prefixes. To use a predefined list of declared namespaces , as Ruchith is doing with the Optimized message parts , or to recursively find all namespaces in the message (that is the default in the implementation).
> Ruchith,
> I think we can make some custom parameter in Rampart-config that will set the strategy to use regarding namespace prefixes. 
> Thanks.
> Regards,
> Angel

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (RAMPART-40) implementation of the Xpath support

Posted by "Angel Todorov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Angel Todorov updated RAMPART-40:
---------------------------------

    Attachment: policy_ut_xpath.xml

Hi Ruchith,

I am attaching one policy example where XPath is used (EncryptedElements).

Regards,
Angel

> implementation of the Xpath support 
> ------------------------------------
>
>                 Key: RAMPART-40
>                 URL: https://issues.apache.org/jira/browse/RAMPART-40
>             Project: Rampart
>          Issue Type: New Feature
>          Components: rampart-core, rampart-policy
>    Affects Versions: 1.1, 1.2
>         Environment: Apache Axis2 1.2,  Rampart-head , tomcat 5.5.23
>            Reporter: Angel Todorov
>             Fix For: 1.2
>
>         Attachments: policy_ut_xpath.xml, svn_diff.txt
>
>
> This is the implementation  (SVN Diff attached) of XPath support - <SignedElements> , <EncryptedElements>. For now there are two ways to retrieve the namespace prefixes. To use a predefined list of declared namespaces , as Ruchith is doing with the Optimized message parts , or to recursively find all namespaces in the message (that is the default in the implementation).
> Ruchith,
> I think we can make some custom parameter in Rampart-config that will set the strategy to use regarding namespace prefixes. 
> Thanks.
> Regards,
> Angel

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.