I've been looking in the template of the Home interface generation (home.j).
There's a fragment like this which generates the create methods:
<XDtEjbSession:ifNotStatelessSession>
<XDtMethod:forAllMethods>
<XDtEjbHome:ifIsCreateMethod superclasses="false">
<XDtMethod:methodComment indent="3"/>
public <XDtEjbIntf:componentInterface type="remote"/>
<XDtEjbIntf:interfaceMethodName/>(<XDtParameter:parameterList/>)
<XDtMethod:exceptionList
append="java.rmi.RemoteException,javax.ejb.CreateException"/>;
</XDtEjbHome:ifIsCreateMethod>
</XDtMethod:forAllMethods>
</XDtEjbSession:ifNotStatelessSession>
IMHO, just changing the value of the attribute superclasses from false to true
should solve my problem (since it would traverse superclasses to look for
create methods), but I'm not sure.
Can anyone tell me? And, if that's a solution, is there any danger in using
this modified template not just for those beans but for all the beans of my
app? I suppose that there's a reason to set the value of superclasses to
false...
Thanks.
Ferran
_______________________________________________________________
Copa del Mundo de la FIFA 2002
El �nico lugar de Internet con v�deos de los 64 partidos.
�Ap�ntante ya! en http://fifaworldcup.yahoo.com/fc/es/
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
