I'm experimenting with some new beans in the xdoclet paradigm. I am not
enamored with the data object pattern and would like to not generate the
dataobjects. It seems I can turn this off by using
@ejb:data-object container="false"
From what I can tell inspecting the code, the template engine should
crawl up the inheritance looking for tags, so that if I I specify that
line in the superclass of the bean class, the data object would not get
generated for the child. That is not the behavior - I have to put that
line in the subclass. Am I doing something wrong, or is this a
bug/feature?
And now for the suggestion. I'm really positive about using xdoclet for
an upcoming rewrite of our app, and I'm doing a bunch of groundwork to
establish conventions and techniques. I would like to see xdoclet take
a strategy of least-invasiveness in its generation. For instance, the
package substitution (moving interfaces into .interfaces if the bean was
defined in .ejb) was on by default, forcing people to add tons of tags
to their code if their conventions differed from this builtin behavior.
(It's now off, which is a good thing.) I believe this should be
extended across the utility, where the ant subtasks avoids nonstandard
things, unless explicitly enabled.
Maybe data objects are the only example of this forced feature set.
Adding COMP_NAME and JNDI_NAME to the Home is not exactly invasive, but
it is pushing someone else's conventions on the rest of the users. But
I'd really like to see data objects turned off by default.
xdoclet.ejb.tags.DataObjectTagsHandler, around line 200
-benJ
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
