A wise old hermit known only as Paul Cantrell <[EMAIL PROTECTED]> once said:
> > Because it's good practise. It separates the business contract > > from the > > technical contract, so you don't have ejbActivate, ejbPassivate etc. > > cluttering up your code > > Huh. I thought that this was the reason -- until I tried it and > it didn't work! I must be missing something...... If I leave > those methods out, it complains that my class isn't implementing > the SessionBean interface. If I don't implement that interface, > ejbdoclet passes over my session bean entirely. You need to declare the class as abstract. That should stop the errors about not implementing all the interface's methods. As you've observed, you still need to say your bean implements SessionBean (or EntityBean, or MessageDrivenBean) so that XDoclet can recognize it as such. Andrew. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Got root? We do. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
