Hi folks,
I started to convert to @ejb:bean tag and have some
problem with it - session and entity have far more
common parameters than message driven.
So it seems that putting all of them into @ejb:bean
( common ones ) does not eliminate need for
@ejb:session @ejb:entity & @ejb:messsage-driven
What about following idea:
We determine what kind of bean is it by inheritance
( implementing of certain interface )
What is wrong , if we follow DTD names in class level
tags
( say, @ejb:name @ejb:description @ejb:small-icon etc.
)?
This would be nice to migrating people, it would not
be
more verbose than tag with a lot of parameters,
and it would be aesy to understand for all -
just look in dtd.
All the tags where just a string value is expected
would be single param, and those like ejb-ref would
use name/param values
We can also wrap references to such class tags with
<XDoclet:requireTag>
<foobar>bazbang</foobar>
</XDoclet:requireTag>
which would bomb to user if he did not specified
this tag required by dtd?
Opiniions?
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-devel
