> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:xdoclet-devel-
> [EMAIL PROTECTED]] On Behalf Of Andrew Stevens
> Sent: Wednesday, August 29, 2001 1:56 AM
> To: [EMAIL PROTECTED]
> Subject: [Xdoclet-devel] Template generation for non-ejb classes
>
> I've been looking at the Toplink persistence framework at work, and
have
> the DTD for their XML project deployment file, so I'm thinking of
trying
> to do an xdoclet task for it (if I ever have time). Now, while it's
EJBs
> I've currently been using it with, it also appears to work just as
well
> with other classes. I'd been wondering, therefore, if it really
belonged
> in the ejbdoclet task, or whether it would fit better as a subtask of
a
> more generic 'classdoclet' task (since if you're not using it with
EJBs,
> you don't need any of the EJB subtasks, in particular the mandatory
> session one).
Probably a classdoclet is a better thing, probably.
> I notice the latest version has some stuff in for SOAP, "with special
> support for EJB beans." This implies that it still works for other
> classes, though (admittedly I haven't used it myself yet), so the same
> might apply to this?
Yes. I used 2-3 tags from AbstractEjbSubTask and btw I thought normally
people will use EJBs and wrap them by soaps, so put it in ejbdoclet,
while maybe webdoclet was also ok since it's called by web clients
mostly! Instead of using Xdoclet:ifIsstatelessSession I could simply do
a isDerivedFrom("javax.ejb.SessionBean") and
ifHasClassTag/ifClassTagValueEquals("stateless") and abandon using tags
defined in AbstractEjbSubTask. So it would be possible to put it in
webdoclet or classdoclet, not deriving from AbstractEjbSubTask (which
expects an EjbDocletContext).
As I said mostly people will use EJBs as soap services, and it's better
to generate soap dds right there in ejbdoclet, it's faster because
ejbdoclet already loaded and finished javadoc-ing the sources, if I put
it in classdoc then classdoc should do loadind/javadocing again.
Maybe the best thing to do is put toplink/soap stuff in ejbdoclet and be
more tolerant in ejbdoclet's impl. I mean smartly include <session/> if
<deploymentdescriptor/> specified, otherwise don't. So, it'll be
possible for user to define something like this:
<ejbdoclet>
<toplink/>
</ejbdoclet>
Anyway, maybe the best thing to do is a xdoclet task with
ejbdoclet/webdoclet/classdoclet elements?! No, it'll be ugly :-)
> On the other hand, depending on what happens in the future for
unifying
> the EJB's persistence tags (instead of each vendor-specific having
their
> own), maybe the TopLink stuff would have to stay in the ejbdoclet task
in
> order to make use of that...
Yes, I agree, though the persistence tags seem to be trickier than I've
thought!
Ara.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-devel
