On Tue, Apr 27, 2004 at 12:07:49PM -0400, graham king wrote: > I'm always hesitant to post for the sake of asking something > silly,but, I don't know where to begin to solve this.
Don't worry about asking "silly" questions. Odds are other people have the same question too. Excuse the delay in responses--we've been working hard on a Geronimo release: http://www.theserverside.com/news/thread.tss?thread_id=25613 > From what I can tell (which I'm still not so sure how it all works) > is that my ejb-jar.xml file defines the ejb fields to use. These are > then mapped to my mysql.cmp_or_mapping.xml file. The CMP layout is basically as such: the openejb.conf points to local and remote database.xml files, the database.xml files point to the mapping.xml. Seems kind of goofy I know, but that is the by product of using a third-party (Castor) for persistence; we don't have the control to offer a simpler view. Odds are, you simply have a disconnect somewhere in the chain. > Here's the exception that I've gotte: > java.rmi.RemoteException: The bean encountered a non-application exception.; nested > exception is: > java.rmi.RemoteException: Attempt to create an entity bean > (DeploymentID="EmployeeBean") that can not be persisted.; nested exception is: > org.exolab.castor.jdo.ClassNotPersistenceCapableException: The class > com.thejanehuts.ejb.employee.EmployeeBean is not persistence capable: no mapping was > defined for the class "no mapping was defined for the class" is Castor JDO's way of saying "I can't find a Castor mapping file for your class" If you are any good with a wiki (I'm not), feel free to dump anything you get working into here http://wiki.codehaus.org/openejb for others to use too. -David
