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

Posted to c-dev@axis.apache.org by "Dumindu Pallewela (JIRA)" <ji...@apache.org> on 2008/10/06 08:09:44 UTC

[jira] Assigned: (AXIS2C-595) XPath support in AXIOM

     [ https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dumindu Pallewela reassigned AXIS2C-595:
----------------------------------------

    Assignee: Dumindu Pallewela  (was: S.Uthaiyashankar)

> XPath support in AXIOM
> ----------------------
>
>                 Key: AXIS2C-595
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-595
>             Project: Axis2-C
>          Issue Type: New Feature
>          Components: xml/om
>         Environment: Any
>            Reporter: Malinda Kaushalye Kapuruge
>            Assignee: Dumindu Pallewela
>         Attachments: xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip
>
>
> We need to have the X-Path support in AXIOM/C. This is essential in many scenarios where we need to specify a particular set of XML nodes. On example comes with WS-Security Policy where we have to specify a particular node that is needed to be encrypted/signed. Due to lack of X-Path support in AXIOM we are forced to find alternative methods. 

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


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