Well - indeed I was reading the ejb docs from ejb 2.x point of view: having ejb EntityBeans. The big difference I did not notice before is, creating an Entity ejb using deployment descriptors or using the @Entity annotation does not result in the same behaviour of the container...
Finally I just have to put the @Entity classes into some jar file which is available by SessionBeans simply via classpath. If I got u right, this perfectly helps. Ty! djencks wrote: > > I think we're getting tied up in nomenclature. With ejb3, the only > ejbs are session beans and mdbs. Something you annotate with @Entity > is not an ejb, just a jpa persistent object. For instance you can > put them directly in a web app and they will work fine. You can also > have "persistence units" with only jpa entities and a persistence.xml > in them that are referenced through manifest classpath of ejb jars or > wars. In any case, a jar with only @Entity classes in it will not be > recognized as a ejb jar and if you claim it is the ejb deployer will > object. > > hope this helps > david jencks > > -- View this message in context: http://www.nabble.com/maven---geronimo-2.0-example-build-problem-tf4496318s134.html#a13132137 Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
