Hi Ad, with release 1.0.1 we (well, at least it was me) started with some refactorings of mapping loaders. Target of these refactorings are major code cleanup of the crapy code involved in loading of castor's mapping as well as provide the possibility to load different mapping formats (JPA, JAXB, mapping through annotations). With 1.0.2 and 1.0.3 we introduced some small changes to public interfaces while there are much bigger changes internally.
What you are hit by is that the Mapping.JDO property and the MappingResolver class are counted to the internals and have never been intended to be used by public. As we view them to be internal both of them had been removed or replaced by some other mechanisms at this refactoring. So the bad story is that I can not tell you a direct replacement of these properties/classes. On the other hand I understand that you needed access to MappingResolver as I used them myself to extract information from Class-/FieldDescriptor in the past. If that is what you are doing with MappingResolver then there is an easy solution. To find the ClassDescriptor of a given Class mapped to a database I have added a static method. Class: org.castor.jdo.util.JDOUtils Method: ClassDescriptor getClassDescriptor(String dbname, Class type) If you use MappingResolver for any other purpose please let us know. Depended on you requirements we may add another lookup method or give you a piece of code to access the same information as before. Regards Ralf [EMAIL PROTECTED] schrieb: > Hi Werner, > > > I don't know why these classes are used this is an old piece of code. The > person that did write this code is no longer working here. > > Met vriendelijke groet/with kind regards, > > > Ad Kerremans > > > > > > > "Werner Guttmann" > > <[EMAIL PROTECTED] To: > <[email protected]> > > com> cc: > > Subject: RE: [castor-user] > problems upgrading to castor 1.0.5 from 1.0 > 15-11-2006 13:21 > > Please respond to > > user > > > > > > > > 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 > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email -- Syscon Ingenieurbüro für Meß- und Datentechnik GmbH Ralf Joachim Raiffeisenstraße 11 D-72127 Kusterdingen Germany Tel. +49 7071 3690 52 Mobil: +49 173 9630135 Fax +49 7071 3690 98 Email: [EMAIL PROTECTED] Web: www.syscon-informatics.de --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
