> -----Original Message-----
> From: Dmitri Colebatch [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, September 08, 2001 6:12 AM
> To: Ara Abrahamian
> Now - re the release... I think we're looking pretty good... and what
I'm
> about to say is partially long term thoughts... you said we need to
make
> some noise about this - and I agree 100%, so how - ant-user
> definately... depending on how the weblogic stuff is we should post
> something on the bea site, they have a lot of message boards... also
> obviously jboss-user, javaworld, theserverside... umm, others? I
would
> also like to get the doco on the site - in the documenation section,
not
> sure how to do it - and as I'm not admin I'm guessing I cant, could
you
> give me admin priv please?
Yes indeed. We should share propagandistic responsibilities and avoid
overlaps :-)
I remember Vincent told me to write an article for JavaWorld about
EJBDoclet. That's definitely a very good idea. I'm not sure XDoclet v1.0
is ready for that :o)
I still have some things in my mind that we should implement. I
postponed it always for the next release. There should be something
useable for the moment, you can then refactor it. So I always thought
"no not yet". But I guess after v1.0 it's definitely the time for that
change. I'm talking about changes to the way we work with template tag
impl methods. You already have seen those two long long SubTask and
AbstractEjbSubTask classes where we put almost 80% of impls there. This
is wrong. We'll go a jsp-taglib-like path but avoid
jsp-heavyweight-ness. Details should be discussed but generally it'll be
like this:
A property file like Ant's where we'll map a namespace name to an
implementer class (<XdtMethod:forAllMethods/> will map to
xdoclet.MethodTags and its forAllMethods method), so we'll break the
functionality to different classes instead of being monolithic.
MethodTags, for instance, will derive from interface xdoclet.Tags (or
maybe AbstractTags class), a well-designed contract is defined there:
init(), setExecutionContext() (sets currentclass for example). As before
tag impl methods will be accessed by reflection, accepting the usual
string/properties param. The template source will change from XDoclet:
to XdtMethod: for example and not more. Note that MethodTags will
implement several tags: forAllMethod/methodType/methodName and so on.
PermissionTags will implement hasPermission/forAllSecurityRoles and so
on. Utility classes such as isSession(ClassDoc) will be public static,
this means you can write your TopLinkTags and TopLinkSubTask
(SubTask-derived classes will serve as a place where you put config
parameter get/set/create methods) and while toplink can be
ejb-independent but it indeed can call isSession static utility method
of SessionTags.
That's the way it should have been designed from day one, but it wasn't
and I just postponed it.
Suggestions are welcome :o)
Ara.
_________________________________________________________
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
