No, not with the current code base (as far as I remember). But I'll be in touch with you on that very subject once I manage to get my head around 1355/1365.
Werner Jon Wilmoth wrote: > The good news is I think http://jira.codehaus.org/browse/CASTOR-1365 and > http://jira.codehaus.org/browse/CASTOR-1355 are closely related and fixing > one may solve the other. Speaking of which...is it possible to allow for > lazy-loaded independent objects NOT be required to be loaded during the same > txn as another object? For example if City has a State/Province object which > in turn has a Country object and all are related through lazy-loaded > independent relationships it would be great to be able to do: > > City city = new City(); > city.setState(stateLoadedInALongTxn); > db.begin(); > db.create(city); > db.commit(); > > Instead of: > > City city = new City(); > db.begin(); > city.setState( (State) db.load(State.class, stateLoadedInALongTxn.getId()) ); > db.create(city); > db.commit(); > > Thanks, > Jon > > ----- Original Message ---- > From: Werner Guttmann <[EMAIL PROTECTED]> > To: [email protected]; Jon Wilmoth <[EMAIL PROTECTED]> > Sent: Thursday, March 30, 2006 11:45:36 PM > Subject: RE: [castor-user] [JDO] ClassNotPersistenceCapableException loading > independent objects > > > Jon, > > Thanks for your patience with our (non)'dealing' of > http://jira.codehaus.org/browse/CASTOR-1365. Having said that, I have never > seen below problem, and I am almost 100% sure that I shall be looking into > the original problem first. > > Werner > >> -----Original Message----- >> From: Jon Wilmoth [mailto:[EMAIL PROTECTED] >> Sent: Freitag, 31. März 2006 09:06 >> To: [email protected] >> Subject: [castor-user] [JDO] >> ClassNotPersistenceCapableException loading independent objects >> >> I'm trying to work around >> http://jira.codehaus.org/browse/CASTOR-1365 by loading the >> independent objects in the same txn prior to calling >> db.create, but now I'm getting another error: >> >> org.exolab.castor.jdo.ClassNotPersistenceCapableException: >> The class ...Person$$EnhancerByCGLIB$$7166e6b7 is not >> persistence capable: >> no mapping was defined for the class >> at >> org.exolab.castor.persist.PersistenceInfoGroup.getPersistenceI >> nfo(PersistenceInfoGroup.java:67) >> at >> org.exolab.castor.jdo.engine.DatabaseImpl.load(DatabaseImpl.java:358) >> at >> org.exolab.castor.jdo.engine.DatabaseImpl.load(DatabaseImpl.java:328) >> at >> ...GolfRoundDetail.loadIndependentChildren(GolfRoundDetail.java:67) >> >> The mapping file does indeed contain a definition for Person >> and it is being loaded successfully elsewhere in the >> application. Werner had mentioned there were duplicate >> generated proxy classes...is this the underlying cause for >> this most recent error? >> >> Thanks, >> Jon >> >> p.s. Suggestions about how to work-around bug #1365 are >> greatly appreciate! >> >> ------------------------------------------------- >> If you wish to unsubscribe from this list, please send an >> empty message to the following address: >> >> [EMAIL PROTECTED] >> ------------------------------------------------- >> >> >> > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
