[jdom-interest] XSLT and JDOM

[philip.nelson at omniresources.com]

> My suggestion for JDOM is that if it is to support efficient 
> XSLT implementation

I think its not ever very efficient to do a transformation by first parsing
into a tree structure like JDOM so I don't know that this would ever rate
very highly as a goal of the api.

> It's more awkward for traversing the nodes in 
> document order, which
> requires recursing down through levels of the tree and 
> getting the list of
> children at each level.

This implementation is at the core of the JDOM api though.  An Element with
all it's children can exist without a parent.

> 
> Traversing the nodes also requires iterating through the 
> children at a level in
> either forward or reverse order (though forward order is 
> probably used much more
> often than reverse order). The proposed change to a SinglyLinkedList
> implementation would keep forward iteration efficient but 
> make reverse iteration
> very expensive.
> 

If XSLT from JDOM was a high priority this would make more sense.  Actually,
nobody was totaly sold on the singly linked list but we couldn't think of a
reason not to do it and save the bytes that couldn't be covered by copying
to a new List that works best for your own needs.