Kai Hackemesser wrote:
Ok, I learned recently, that Saxon isn't implemented in JDK 1.4.2 but
Xalan. The requirement is avoiding additional libraries as far as
possible. Means I can't use anything where I have to argue about
adding another library at first. Pure JDK 1.4.2 means virtually
nothing what isn't inside of rt.jar by default. Beside of the company
written code, of course.
I've no idea why in these days of reuse, one would want to choose *not*
to use additional libraries. You don't bake your own bread just because
you happen to have some flower in the closet. It seems to me the common
misconception that when you get it elsewhere, it is bad or dangerous,
whereas the opposite is usually true and the benefits (both in time,
maintenance and costs) far outweigh the additional overhead of an extra
library. I'd opt for another job if you can't choose the tools that best
fit a task ;)
Btw: afaik with Xalan you can build extensions, yes, but I don't
remember how.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--