There is a fundamental question for the plugin: is it a goal to have tag compatibility with XDoclet1?
I'm struggling to understand the positioning of the XDoclet1 and XDoclet2 plugins. As a user, why should I choose one over the other? When I read the XDoclet2 documentation, it promotes XDoclet2 as being easier to write plugins for. Well, that's great for the plugin developers, but as a user I care more about features (e.g. union-subclass), and compatibility (to ease migration pain).
Of course, if compatability is a design goal, then how will the evolution of the XDoclet1 and XDoclet2 plugins be kept in step? Are the XDoclet1 plugins still under active development?
Sorry, lots of questions and no answers :-(
John
Anatol Pomozov wrote:
Oops sorry
+1 @hibernate.key -> @hibernate.collection-key
Anatol Pomozov wrote:
I cant help you with such tool.
But we can decide what to do with Xdoclet1 - 2 incompatibility. The main reason in doclet-tag naming was accordance
with xml tag names. That is why we use @hibernate.key-property instead of @hibernate.collection-key.
But personnaly for me @hibernate.collection-key also a good name.
John, is it full list of differencies between xdoclet1 and 2?? If yes we can change the doclet names.
So I
+1 @hibernate.key-property change to @hibernate.collection-key
-0.2 @hibernate.collection-one-to-many change to @hibernate.one-to-many
I don't like collection- prefix in doclets because one-to-many is quite informative name.
John Latham wrote:
Hi,
For my project right now, the Hibernate plugin for XDoclet seems better than the equivalent for XDoclet2 (or perhaps I'm not using the right tags yet). So far, I've gone from XDoclet->XDoclet2 and back again
I would like to switch back and forth like this as both systems develop. This is painful, as the tags are incompatible but share the same "namespace" (@hibernate) so should not co-exist in the same source files (or perhaps I should just ignore warnings during mapping file generation!).
I end up doing a load of find/replace, for example,
@hibernate.collection-key -> @hibernate.key-property @hibernate.one-to-many -> @hibernate.collection-one-to-many
Maybe I'll write some sed scripts to do this, but maybe some tools exist already for tag migration..?
Regards John Latham
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
xdoclet-plugins-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
xdoclet-plugins-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
xdoclet-plugins-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ xdoclet-plugins-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
