Re: [xsl] Xpath vs xslt vs jaxb within java context

Subject: Re: [xsl] Xpath vs xslt vs jaxb within java context
From: "Michael Kay mike@xxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 9 Feb 2016 10:03:54 -0000
> On 8 Feb 2016, at 17:15, Mailing Lists Mail daktapaal@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Dear all,
> I work in a java development environment where I am often challenged about
what us the right technology to use.
> hould I use jaxb on the xml and get the information that I want using the
java objects ...
> ## should I use xpath API to get the information that I want
> ## should I call in an xslt file for getting what I want ?
>
> Are there any guidelines on when to use what ? What are best practices ..
what are the arguments for and against these approaches ? All your experiences
will count for me .. any information on performances , efficiency etc is what
I am looking for ..
>
>

In my experience JAXB works really well for XML vocabularies that are small,
simple, and stable. Then people get lulled into using it for large, complex,
or changing XML vocabularies, and they find themselves in a nightmare of
managing thousands of changing Java classes, sometimes big enough to blow the
compiler.

If you're going to use a generic tree model, then the best advice I can give
is that there's a wide choice available, and the worst choice of all is DOM.
My preferences would always be JDOM2 or XOM. The only reason people use DOM is
that it's perceived as standard. But it's horrible.

Michael Kay
Saxonica

Current Thread