Matthias Wessendorf wrote:
hi,
But I see xdoclet not as the tool to cover all, it is more a tool to
give you a good headstart and manages for you the error ridden gruntwork
yes, one of the main points of xdoclet is to generate the tld ;) In
the past there were twotimes or so an error that a strict container
(was it weblogic) couldn't deploy MyFaces because tld was not
*correct* to its corresponding components.
As I started to look at Jiris code to bypass it into MyFaces code
base, I looked a bit into the xdoclet stuff, and I liked the stuff
what I saw there. Also it is ok to apache projects to include
xdoclet.jar, since their licence is compatible to apche2.0. (I asked
that issue on a special apache mailing list that time)
The main problem with xdoclet1.0 is, that it is sort of legacy stuff,
xdoclet1.0 has a lousy template language (believe me it is really lousy,
I have written a dozen templates so far with it)
and it has its quirks with JDK 5.0, in my work project I still use
xdoclet 1.0 but if I can follow the JSF route in the long term (there
still is inhouse discussion going on because I am sort of a lone coder
with that stuff here), I will definitely move to 2.0 for maintenance
reasons and because of the 5.0 incompatibility (which has not been a
show stopper, for now).
The main development currently is going on with xdoclet 2.0 which uses
velocity as templating language, the main problem with xdoclet 2.0 is
not that it is not production ready, but the documentation currently
lacks severely and there are simply to few plugins available, so the
devs don�t dare to brand it a release currently.
If you follow the mailing lists, the devs themselves believe, that you
can put it into production use.
So if there is any effort towards xdoclet in the near future, dont use
xdoclet 1.0 anymore but go straight for 2.0, if you dare.
