I meant to ask--what alternatives do you suggest to that avoidable second step as far as getting to the XSLT processor?
Create SAX events directly from the DB query result. Unless you have some non-trivial calculations or you know you can benefit from caching, don't use entity beans. Well, entity beans don't have much advantage even in this cases. Use sorting and grouping features of the DB.
J.Pietschmann
