The missing imports are because the imports are the interfaces that you are generating.
The tests use the local or remote interfaces of the EJBs, but the interfaces simply haven't been generated yet. This isn't really a problem, and there isn't really a way around this. Nice to see your attitude has improved towards open source projects (http://jboss.org/forums/thread.jsp?forum=141&thread=20349&message=3738032&q =Edward+Kennedy#3738032) :) -----Original Message----- From: Edward Kenworthy [mailto:edward@;kenworthy.info] Sent: 23 October 2002 12:59 To: [EMAIL PROTECTED] Subject: [Xdoclet-user] xdoclet problems, problems, problems. Ok so after all the problems trying to use xdoclet with my own code I thought "I know, I'll try the samples - they'll work." How wrong could I be. How can you have any confidence in a tool (and how can you be using it?) when the samples won't compile without errors and the deployment descriptor it generates is fucked ? Specifically JBoss says this, several times: 12:51:38,766 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=ejb/bank/Customer,service=EJB org.jboss.deployment.DeploymentException: primkey-field must be the same type as prim-key-class at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCCMPFieldMetaData.<init>(JDBC CMPFieldMetaData.java:130) and the build file says this, also several times: [ejbdoclet] Constructing Javadoc information... [ejbdoclet] /usr/local/xdoclet/xdoclet-1.1.2/samples/src/java/test/ejb/ AccountBean.java:7: Class test.interfaces.Account not found in import. [ejbdoclet] import test.interfaces.Account; [ejbdoclet] ^ [ejbdoclet] /usr/local/xdoclet/xdoclet-1.1.2/samples/src/java/test/ejb/ AccountBean.java:8: Class test.interfaces.AccountData not found in import. [ejbdoclet] import test.interfaces.AccountData; [ejbdoclet] ^ [ejbdoclet] /usr/local/xdoclet/xdoclet-1.1.2/samples/src/java/test/ejb/ AccountBean.java:9: Class test.interfaces.Customer not found in import. [ejbdoclet] import test.interfaces.Customer; [ejbdoclet] Now correct me if I'm wrong - but ALL of these errors are in generated code, aren't they ? Now despite all the evidence I find it hard to believe that xdoclet is really this bad - so what really obvious thing, not to be found in the samples' readme or the documentation, am I missing ? Edward ------------------------------------------------------- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
