[Erez]

I’ve upgraded to Eclipse 3.0.1 + ME3.8.2

Now I try to run XDoclet on my Logic EJB module and I get the error:

“XDoclet classpath missing J2EE classes”

Buildfile: c:\dev\datebar\Logic\xdoclet-build.xml
N10004:
[ejbdoclet] Deploy TEMPLATE URL: jar:file:/C:/Program%20Files/MyEclipse/eclipse/plugins/com.genuitec.jboss.ide.eclipse.xdoclet.core_3.8.1/xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-deploy_wsdd.xdt
[ejbdoclet] Undeploy TEMPLATE URL: jar:file:/C:/Program%20Files/MyEclipse/eclipse/plugins/com.genuitec.jboss.ide.eclipse.xdoclet.core_3.8.1/xdoclet-apache-module-1.2.jar!/xdoclet/modules/apache/axis/ejb/resources/axis-undeploy_wsdd.xdt
[ejbdoclet] XDoclet classpath missing J2EE classes
[ejbdoclet] at xdoclet.modules.ejb.EjbDocletTask.validateOptions(EjbDocletTask.java:85)
[ejbdoclet] at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:94)
[ejbdoclet] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[ejbdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
[ejbdoclet] at org.apache.tools.ant.Target.execute(Target.java:341)
[ejbdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[ejbdoclet] at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[ejbdoclet] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:379)
[ejbdoclet] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:135)
[ejbdoclet] Caused by: Make sure the jar file containing the javax.ejb.EntityBean class is on the classpath specified in the <taskdef> that defined ejbdoclet. These classes are needed in order to generate correct output.
[ejbdoclet] at xdoclet.DocletTask.checkClass(DocletTask.java:508)
[ejbdoclet] at xdoclet.modules.ejb.EjbDocletTask.validateOptions(EjbDocletTask.java:82)
[ejbdoclet] … 8 more
[ejbdoclet] — Nested Exception —
[ejbdoclet] Make sure the jar file containing the javax.ejb.EntityBean class is on the classpath specified in the <taskdef> that defined ejbdoclet. These classes are needed in order to generate correct output.
[ejbdoclet] at xdoclet.DocletTask.checkClass(DocletTask.java:508)
[ejbdoclet] at xdoclet.modules.ejb.EjbDocletTask.validateOptions(EjbDocletTask.java:82)
[ejbdoclet] at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:94)
[ejbdoclet] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[ejbdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
[ejbdoclet] at org.apache.tools.ant.Target.execute(Target.java:341)
[ejbdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[ejbdoclet] at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[ejbdoclet] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:379)
[ejbdoclet] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:135)
BUILD FAILED: C:\dev\datebar\Logic\xdoclet-build.xml:32: Unexpected error
Total time: 3 seconds

Please help,

Erez

[Erez]

I solved it by deleting the xdoclet-build.xml on both the Logic EJB module and the Web module. then regenerate them by going into the module’s properties/xdoclet and pressed ok which regenerated them.
Only then the xdoclet build was working fine.

Isn’t there something that can alert such a problem in advance?
Sorry to bother the support forum but still..

Erez

[Greg]

Erez,

We don’t currently have an mechanism in place to warn about a stale xdoclet-build.xml file. You did exactly the right thing if some part of your environment changes and the xdoclet-build file needs to be regenerated. We are in the planning stages for 3.9. One possibility would be to generate the xdoclet-build file each time xdoclet is run so this problem never happens.

[Erez]

That could be the easiest way since I don’t think this file gets too big and so regenerating it would not take so much time. Nevertheless I would try and think of another less blunt way to do that.

Erez

[Author]

Posts