Werner, Thank you for your response. After all, I resolved this issue using a different strategy: I load the file using JDOM and try to load the classes, filtering the ones that are not found in the classpath. Then, passing just the mappings of the classes that are in the classpath everything works fine.
Thanks everybody. Marcio Kuchma On Fri, Mar 21, 2008 at 5:14 AM, Werner Guttmann <[EMAIL PROTECTED]> wrote: > Marcio, > > right now, in Castor XML there's no way to have mappings lazy-loaded. I > guess this is a result of users generally wanting to know if they have got > their mapping wrong at *startup* time, and not some when later on. > > Imagine a situation where you've got a long-running application deployed > with a mapping file that has an error. I guess you wouldn't not like a > situation where it would take days to figure out that for that one class > (un-)marshalling doesnot work. > > Regards > Werner > > Marcio Kuchma wrote: > > > > > > > > > Hi, > > > > I have a problem and would like to read your opinions about it. If > > this issue is documented somewhere, please let me know (I've been > > searching through the documentation and mailling lists, without > > success). > > > > I have a mapping file with (e.g.) ten classes mapped. This mapping is > > used in different projects. Some projects have all the ten classes in > > the classpath and some doesn't. > > > > The projects that contain all the classes work fine. In the projects > > that doesn't have all the classes in the classpath, the Castor throws > > an Exception when I'm initializating the Marshaller with the mapping > > file: > > > > org.exolab.castor.mapping.MappingException: Could not find the class > > model2.TesteModel2 > > at > org.exolab.castor.mapping.loader.MappingLoader.createDescriptor(MappingLoader.java:420) > > at > org.exolab.castor.xml.XMLMappingLoader.createDescriptor(XMLMappingLoader.java:227) > > at > org.exolab.castor.mapping.loader.MappingLoader.loadMapping(MappingLoader.java:313) > > at org.exolab.castor.mapping.Mapping.getResolver(Mapping.java:292) > > at org.exolab.castor.mapping.Mapping.getResolver(Mapping.java:247) > > at org.exolab.castor.xml.Marshaller.setMapping(Marshaller.java:561) > > at XmlSerializer.getMarshaller(XmlSerializer.java:68) > > at XmlSerializer.serialize(XmlSerializer.java:51) > > at TesteProblemaCastor.main(TesteProblemaCastor.java:31) > > > > The classes that aren't in the classpath are not used by the project. > > So, except by the Castor initialization, everything could work > > correctly. > > > > After all, this is my question: is there a way to instruct Castor to > > do "lazy loading" of the mappings? > > > > I'm using the version 0.9.9.1 (yes, really). > > > > Thanks. > > > > --------------------------------------------------------------------- > > 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
