As far as I know, some of these classes have been refactroed recently. But let's wait to see what Ralf has got to sa. Having said that, I'd be interested to learn what you are trying to achieve by using that code. In other words, I would not expect that a user of Castor JDO would try to use these classes.
Werner > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 15. November 2006 13:14 > To: [email protected] > Subject: [castor-user] problems upgrading to castor 1.0.5 from 1.0 > > Hi, > > I replaced the Castor 1.0 jar with the 1.0.5 jar. > My project is complaining that the classess MappingResolver > and Mapping.JDO cannot be resolved > > my imports are: > > import org.castor.jdo.engine.AbstractConnectionFactory; > import org.castor.jdo.engine.DatabaseRegistry; > import org.exolab.castor.jdo.*; > import org.exolab.castor.mapping.*; > import org.exolab.castor.mapping.loader.ClassDescriptorImpl; > import org.exolab.castor.persist.spi.Complex; > > Piece of my code: > > AbstractConnectionFactory cf = > DatabaseRegistry.getConnectionFactory(getDatabase().getDatabas > eName()); > MappingResolver mappRes = cf.getMapping().getResolver(Mapping.JDO); > > > Met vriendelijke groet/with kind regards, > > > Ad Kerremans > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
