Konstantin Priblouda wrote:
Just a reminder:
you are on a wrong list. This list is intendet for
core xdoclet, and plugins are discussed in another.
see
Thanks, I'll copy the original to the plugin list, but comments on your
reply are below.
I'm curious what you think of trying to keep the
hibernate tagnames
matching the mapping DTD one for one.
We try hard to achieve this. But given speed oh
changes in hibernate DTDs it is not easy...
Agreed!
For example, <join> has a <key> subelement in the
mapping DTD, so I
would prefer to have hibernate tags named
@hibernate.join (which we
have) and @hibernate.key (which is currently
join-key instead).
If it is the same element and receives the same
parameters, it shall keep the same name...
If possible...
Yet, above I've given an example where it is possible, yet does not keep
the same name...
There are also several hibernate collection tags in xdoclet 1 that were,
in my opinion, unneccessarily created. Keeping the tag names identical
to the mapping elements would have been preferable. I haven't looked in
xdoclet 2 to see of those collection tag names have been carried over.
Are you commiter of XD1? ( Me too, but I'm inactive
since switching to XD2 completely )
Yes, I'm interested in keeping xdoclet1 alive because I perceive a lack
of momentum in xdoclet2 and it's a harder sell at a corporate level to
get x2 approved as a build tool.
I'm still wondering why people still use XD1 for
hibernate ( ok, XD2 plugin for EJB is not usable
due to lack of use case of developers )...
...exactly. Basically, it's the apparently complete split between
xdoclet 1 and 2, and the xdoclet 2 website leads one to believe that
it's in early alpha or dying. There are no released distributables that
the masses can download, unzip, and go.
It's that simple.
