> Ara, > 1) I believe that simply getting "[ejbdoclet] ..." output suggests that > ejb.jar is in the classpath. You concur?
Maybe no. Maybe it checks for "javax.ejb.EntityBean" for example, doesn't find it and assumes you're deriving from ejb.test.EntityBean (current package). > 2) Yes, I DO get Lots of messages like (exactly same as) > '[ejbdoclet] Running <strutsForm/> > [ejbdoclet] Generating Struts Form classes for 'test.ejb.PersonBean' But not Generating PK class for 'test.ejb.PersonBean' and like that. strutsForm works and it generates stuff for classes derived from EntityBean (but why only for PersonBean?!) so my conclusion is that your classpath is ok. The other possibilities are: it has already generated them all and skips generating again (look at samples/gen-src folder, what's there?) or something very strange or you modified the build file. Start from a clean distro and do only what's required as described in readme doc. It *should* work, because for 1000s of people it has worked. > 3) There IS an Accoount.java generated in ...gen-src/java/test/interfaces > but NO Account.CLASS ANYWHERE (see first described error below). Does > [ejbdoclet] look for a .java or .class file? .java But hey! You don't have to modify anything in build/bat/xml. Just copy the jars and build! > followed by many similar errors "[ejbdoclet] ... cannot resolve symbol". It's ok, typical javadoc warnings. It's garbage, ignore them. V1.2 doesn't rely on javadoc anymore and hence no warnings like that. Ara. _______________________________________________________________ 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
