Howdy yall,
I'm not sure this should go to the dev list, but since it's CVS version I'm
using, I figured I should say it here.
After I did a CVS update today, I found that my base classes form my beans
was getting parsed even though they are not in the list of files.
My xdoclet tag in my build.xml file explicitly has
<fileset dir="${java.src}"> <include name="**/*Bean.java"></fileset>
And my classes are:
public class CustomerBean extends EntityBase
(Where EntityBase implements the EntityBean, and defines some common stuff
(like log objects, etc)).
Yesterday, this worked fine, beans were generated with no problem, but as of
today (I did a CVS update an hour ago), I get build errors saying that
EntityBase doesn't have a @ejb:bean tag.
So, I'm guessing that something is ignoreing the fileset, or figuring out
that CustomerBean extends EntityBase and attempts to parse it.
I figured I could just add:
@ejb:bean generate="false" name="EntityBase" //XDoclet chokes if there's no
name attribute, although it shouldn't since I told it not to generate
to the base class. But then another problem occurs, CustomerBeanData
attempts to extent EntityBaseData (which doesn't exist, since
generate="false")
So, my question is, does anyone know what changed? Or where I should start
looking to fix this? I just started using XDoclet this week, so I'm not
super familure with the code structure.
I'd be happy to fix it and submit the patch, I just need a little hint on
where to look.
Thanks,
-David Budworth
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel