At 00:55 08/11/2002 +0000, you wrote:
Thanks for the feedback guys. You confirmed what I thought might be the case. We'll see how it goes with the 20 odd students next week.A wise old hermit known only as Konstantin Priblouda <[EMAIL PROTECTED]> once said:> > Also, has anyone used xdoclet to teach ejbs? > > Kind of. I had to lead team of 4 developers > who received short training in java. > ( and no formal CS education at all) - > I was able to get them to write EJBs > > > I may be overreaching here, but I was going to give > > a few general lectures > > on ejb, and then do one on xdoclet, before going > > onto specifics of entity, > > session, message beans. > > XDoclet would be really good strarting point, > because it allows to forget about wirting > all the interfaces & dds - so people just > see results coming fast and start to undertand > what EJB is. Later you can provide more details > about DDs etc. Actually, I'd say do it the other way i.e. teach the basics of EJBs first, then show how XDoclet makes it much easier. If you want to get them coding sooner, teach them XDoclet first. If you want them to appreciate what's going on behind the scenes better, teach them EJBs, then show them the benefits of using XDoclet to produce them. > > I'm thinking that if the students only need to focus > > on one file, and not > > on three or more, then it should be more > > understandable, and easier. We'll see. Easier to understand the business logic. Harder to understand the EJB architecture, I'd say. Just my opinion, based on observations of a couple of our developers: One of our guys just got back from a J2EE course, and is now going back through the XDoclet-enhanced code he was previously working on, trying to figure out exactly what it's been doing all this time and how it fits into the EJB architecture ("So the Bean class isn't actually the EJB class in the deployment descriptor, then?", "If this is a stateless session bean, shouldn't there be an ejbCreate() method?", ...) Another developer read up on EJBs first, and tried writing a few (one session & a couple of entities). I rewrote them to use XDoclet, and showed him how much less code they needed. Then I pointed out he won't be getting any more errors on deployment that the remote interface and EJB class methods don't match (at one point, he'd forgotten to add his custom exception to the remote interface's method) :-) Overall, I reckon the second guy's found it easier and is now the bigger XDocletphile. On the other hand, two people's hardly a representative sample. YMMV. Andrew.
cheers,
Bruce
Dr. Bruce Scharlau
Dept. of Computing Science
University of Aberdeen
Aberdeen AB24 3UE
01224 272193
http://www.csd.abdn.ac.uk/~bscharla
mailto:scharlau@;csd.abdn.ac.uk
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
