Hi Godmar,
similar to other XQuery processors, BaseX uses its own internal XML representation, which is much more efficient than the classical DOM representation, esp. if several megabytes or gigabytes are to be processed. Next, as most of our users end up using our own APIs, we haven't put more effort into XQJ. Feedback like yours, however, is welcome to see how XQJ is used in practice, and it might give us some ideas how to possibly extend it in future.
As we have limited resources, just as every other open source project, code patches and external contributions are welcome.
Christian
On Sun, Jul 11, 2010 at 10:26 PM, Godmar Back godmar@gmail.com wrote:
Hi, the Elements returned by XQResultItem.getNode() don't appear to support the EventTarget interface: org.basex.api.dom.BXElem cannot be cast to org.w3c.dom.events.EventTarget This means we need to serialize the node to an XML string, then parse that string to obtain a org.w3c.dom.Node instance that supports this interface. This is awkward and highly inefficient. Why doesn't BaseX support EventTarget (or use the existing DOM implementation provided with Java, which does support DOM events?) - Godmar
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk