-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I assume no one had answered this email.

Anyway, yes we build the whole object model internally to provide XPath
support. We have not implemented XPath on top of AXIOM or Stax. We
simply plugin in Jaxen document navigator mechanism to provide XPath
support.

Couple of things to note here. Most of the queries that we encounter
requires the whole model to be build. So the 90% case looks at the whole
object model. If we try to optimize for the 10% case, then that might
lead to performance drawbacks of the system.

These days I am looking at some of the techniques in SDI systems
(Selective Dissemination of Information) to be used inside Axiom. But I
am yet to find an efficient way to do this with a pull parser. Most of
them tries to exploit on the shared paths of the queries, but I think we
won't execute more than couple of XPaths against a given object model.
So if you find a better way of implementing XPath over Axiom, please do
let us know or even help us by implementing it.

Thanks,
Chinthaka

Angel Todorov wrote:
> Hi all,
> 
> I can see AXIOM has support for XPath. But beneath it is a StAX
> parser, and such pull-parsers don't have random access support for XML
> documents, by design.
> 
> So my question is: Do you call build() on the OM Tree that one wants
> to lookup with XPath? That is, do you cache everything in memory in
> order to support such xpath operations, or you preserve the full
> advantages of a pull-based parser ?
> 
> Thank you in advance.
> 
> Regards,
> Angel
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGKvB7jON2uBzUhh8RAkJEAJ9yqlA0nstaPTqjLJ29+Y/tMwT3RwCdF03i
/jAVEytjTZuXHGrhfuwxNW0=
=9Fqs
-----END PGP SIGNATURE-----

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

Reply via email to