RE: [Xdoclet-user] Session bean pattern

[Ara Abrahamian]

Title: Session bean pattern

Create a custom template file which generates the subclassed blablaEJB class. Shouldn’t be hard. I assume DoSomething is an @ejb:interface-method, so create a very simple template which loops over all method, checks ifIsInterfaceMethod and generates the method with the super call in the body. Take a look at xdoclet’s .j files, docs/architecture.html and also xdoclet-user archives where you’ll find lots of templates/ideas.   Ara. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of James Hughes Sent: Thursday, January 24, 2002 8:51 PM To: '[EMAIL PROTECTED]' Subject: [Xdoclet-user] Session bean pattern   I would like to use this pattern to turn pojo's into session beans: Start with: // not abstract // doesn't implement anything public class WorkerBean {         public void DoSomething(String s){                 ...         }         public String DoSomethingElse(String s){                 ...         } } And have xdoclet gen something like this: public class WorkerEJB extends WorkerBean implements implements SessionBean {         private SessionContext sessionContext;         public void DoSomething(String s){                 try{                         super.DoSomething(s);                 }                 catch(Exception e) { throw new EJBException(e); }         }         public String DoSomethingElse(String s){                 try{                         return super.DoSomethingElse(s);                 }                 catch(Exception e) { throw new EJBException(e); }       }                 public void setSessionContext(SessionContext context){this.sessionContext = context;}         public void ejbRemove(){}         public void ejbActivate(){}         public void ejbPassivate(){} } ...along with the remote interface and the home stuff, etc. Can I do this now with xdoclet?  If not, how hard would it be for me to change it?  Could I do this with just a custom merge file, or by subclassing some of the tasks? I like to use this pattern because it allows me to unit test the business logic within the regular beans outside the app server context.  Any criticism of this way of writing EJBs would also be very welcome. Thanks, Jim Hughes RIA