Kannan V penned
> All my beans are extendig from a parent bean which is implementing
> SessionBean.
I'm doing the same thing. What you want to do is actually tag your base
session bean (see mine below) *and* include it in the FileSet to be
processed.
/**
* Base session bean facade for entity beans.
*
* @ejb.bean type="Stateless"
* generate="false"
*
* @ejb.interface generate="false"
* @ejb.home generate="false"
*/
public class BaseEntityFacadeEJB implements SessionBean
I also have all subclass session beans extend this class *and* implement
SessionBean. I seem to recall the second part was necessary, but you can
try without it.
The three generate="false" tags will set up your interfaces to the
extend the standard EJB ones and force XDoclet not to generate artifacts
for the base bean.
--
David Harkness Sony Pictures Digital
Sr. Software Engineer 310.482.4756 [EMAIL PROTECTED]
Those who judge the value of advice by its source
will at once dismiss the best and follow the worst.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
