Hi all,
Following Axis supports are added
child ,attribute, descendant,
Descendant-or-self,following,following-sibling,self
So this takes XMLStreamReader as input and gives resulting outputs as
OMElements. This will reduce the overhead of building complete OMElement
from XMLStream and it only builds the result.
As next steps I have planned to improve test cases and integrate this in to
Synapse.
thanks
isuru
On Tue, Jun 25, 2013 at 11:55 PM, Hiranya Jayathilaka
<[email protected]>wrote:
>
> On Jun 14, 2013, at 7:40 PM, Isuru Ranawaka <[email protected]> wrote:
>
> Hi
>
> This project will be used in Synapse content based routing in order to
> increase the performance of the XPath evaluation. Up to now it is supported
> for following kind of XPath queries.
> /step/step
> /step/step[number]
> /step/step[name relation
> value](relation : = or !=)
> so as next steps i have planned to do the following
>
> Do more test on above implementations.
> Improve and Optimize code
> Do performance test with current
> AxiomXpath
> Developed API for integrate with
> Synapse.
>
> For develop the API I have to know the following facts.
>
> When OMElement is received for XPath evaluation it may or may
> not matches with the query.if it is matched what will be the output.Is it
> OMElement build from the result or exact OMElement received for evaluation
> or may I need to develop methods for get both when needs?
>
>
> I think your API should just return the OMElement resulting from the XPath
> evaluation. Check the SynapseXPath class.
>
> Thanks,
> Hiranya
>
>
> thanks
> isuru
>
>
>
>
>
>
>
>
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB; http://cs.ucsb.edu
> E-mail: [email protected] <[email protected]>; Mobile: +1 (805) 895-7443
> Blog:
> http://techfeast-hiranya.**blogspot.com<http://techfeast-hiranya.blogspot.com/>
>
>
