Hello all,

New Xdoclet user here, and I'm psyched!  This is a
truly valuable tool.

Anyway, you may have seen a post from me a few days
back regarding support for 1.1 CMP for Weblogic.
Around that time, Aslak checked in some code to
support this, and asked for my help testing it.  So I
pulled it down and took a look, and have some
questions & feedback.

First I'm wondering about support for <finder> in
weblogic-cmp-rdbms-jar.xml.  This is a tag used by
weblogic to define finders, and uses a proprietary
query language.  The new code has a new template
(weblogic-cmp-11-finders.j) that is merged into the
main template.  In this new template, it looks to me
like a <finder> element is added for every
method-level tag "weblogic:finder" that is found.   

I'm not sure how this can work; my understanding is 
that to have a method-level tag, you have to have a
method.  So that means you'd have to declare (and
implement) an actual finder method in the XXXBean
class, right?  But doing that goes against the whole
point of using the <finder> element, which is that you
don't have to write code for simple finders -- the
query language does it for you.

I'm pretty new to EJB development AND XDoclet, so
forgive me if I'm missing something obvious.  But I'm
wondering if class-level tags (analogous to
@ejb:finder, but specific to weblogic) would make more
sense.  

The one other problem I'm having is with the
<persistence-type> and <persistence-use> tags in
weblogic-ejb-jar.xml.  These are hardcoded to 6.0, but
seem to need to have the value 5.1.0 for CMP 1.1 on
Weblogic.  That doesn't look like a hard fix.

Anyway, that's where I'm at.  I'd be glad to dive in
and take a whack at these fixes, if you guys think the
approach is right.

tia,
Mike


__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to