|
First, check that Middlegen supports
your EJB container.
The EJB container's error message should give you an indication about
something wrong either in a deployment descriptor, a Java class or
in the environment.
If you can get the EJB to deploy correctly by modifying the source code
generated by Middlegen (perhaps adding a tag), then
there is obviously something wrong with Middlegen. Only in this case should
you post a bug report to Middlegen.
If you can't get your EJBs to work no matter how you modify the Middlegen-generated
sources, there might be something wrong with XDoclet. You should seek help in the
XDoclet forums.
Remember that XDoclet doesn't care/know whether a source class was written by a human or
by Middlegen, so XDoclet's developers probably don't either. Include a snip of the @tags,
generated (bad?) code and your <ejbdoclet> task.
It's also important to realise that different EJB containers
implement CMP and CMR in their own way. For example, JBoss 3.0.0 will choke
on CMP filelds that are mapped to columns that also participate in a CMR.
This means that for certain schemas you will be able
to generate EJBs for certain EJB containers, while others will not be able to
deploy them correctly.
|
