Unit test with auto-generated interface generates illegal code

In my class diagram I create a persistent class named “Foo”. These files get generated:
interface Foo {...}
class FooImpl implements Foo {...}

Next I set up a persistent test for Foo. On the class diagram I see <<Persistent Test>> FooPersistentTest connected to Foo.

Then I design objects for the test. My FooPersistentTest object diagram has a single foo:Foo object. When I save everything, FooPersistentTest.java is created with this initObjects():

private void initObjects() {
org.hibernate.Session session = persistenceHelper.getSession();
org.hibernate.Transaction tx = session.beginTransaction();
foo = new com.xyz.myproject.model.Foo();
session.save(foo);
tx.commit();
persistenceHelper.closeSession();
}

This code generates an error since com.xyz.myproject.model.Foo is an interface and can’t be instantiated.

See forum

Javadoc above class definition is replaced

I have removed the @generated tag from the javadoc above my class' definition. I added a new method to that class in its class diagram and the javadoc I wrote was removed and replaced with just an @generated tag.

I thought the idea of removing the @generated tag was so that the javadoc couldn’t be changed by the code generator???

See forum

English grammar does not work on the Hibernate 3 platform

Platform = “Hibernate 3”.
A <<Persistent>> class with association * frogs gets generated code “addFrogs” instead of “addFrog”.

See forum