>> Why? > > 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. >> Can I turn this off? > > Possibly. What version are you using? With the current CVS, > just leaving > out the <session> subtask should be enough. With some of the earlier > versions (I forget which) it was a mandatory subtask and couldn't be > disabled. OK, I see that this works. Reasonable. Paul ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
