[jdom-interest] JDOMTransformer

[Jason Hunter]

> >b. Two other transformation "types" are possible: Document -> List
> >and List -> Document. But as XSLT does not guarantee the output is a
> >well-formed document, why not stick to only 2 transform methods,
> >both returning a List ?
> 
> I agree. This is sensible. There is no guarantee that an XSLTransform
> returns a complete Document. Both methods should return a List.

Rusty, in your class examples what percentage of transformations don't
return a document?

> The question here is what the performance cost of allocating a new
> Transformer object is. Certainly it's less than creating by parsing
> the stylesheet from scratch, but perhaps it's still significant. In
> general, nothing in JDOM promises thread safety. Is there a benchmark
> in the house?

Dunno.  I'm guessing it's as fast as an object allocation, which should
be very fast relative to the overhead in a transformation.  But gut
guessing isn't good at predicting true performance.

-jh-