Michael, I forgot to tell you that the resolve() and resolveXml() methods are the ones that get called during un-/marshalling to find the descriptors needed for that process.
Ralf Michael Crozier schrieb: > > Tom & Ralf, > > Thanks for the answers. > > One additional question: Is ClassDescriptorResolver not thread safe > during the use of the Unmarshaller and Marshaller objects, or just > during the construction? > > For example, if I locked the ClassDescriptorResolver during the > invocation of marshaller.setResolver(), would that provide thread safety? > > Or is the opposite true, that I need a distinct ClassDescriptorResolver > for each Marshaller and Unmarshaller object that is being used > concurrently? > > If the latter is true, then I will likely maintain thread-local > ClassDescriptorResolver objects. > > Thanks again, > > Michael > > >> Hi Tom, >> >> you are right that the XML best practice document should point out that >> ClassDescriptorResolver is not thread safe. Sorry for that confusion. >> I'll take care to update docs or make ClassDescriptorResolver thread >> safe for next release. >> >> Regards >> Ralf >> >> >> Carey, Tom schrieb: >> >>> This link below talks about reusing ClassDescriptorResolvers to >>> achieve best >>> performance. Is this link suggesting that it is thread-safe? If so, >>> maybe >>> this page should be updated. >>> >>> http://www.castor.org/xml-best-practice.html >>> >>> Tom >>> >>> -----Original Message----- >>> From: Ralf Joachim [mailto:[EMAIL PROTECTED] >>> Sent: Friday, November 03, 2006 2:50 AM >>> To: [email protected] >>> Subject: Re: [castor-user] ClassDescriptorResolver & thread safety >>> >>> Hello Michael, >>> >>> as far as I can see when looking at the source of >>> XMLClassDescriptorResolver >>> it isn't thread safe by design. While I think there should be no >>> problem if >>> all ClassDescriptor's are loaded before starting to un-/marshal, I'd >>> suggest >>> to go safe and use them in a thread safe way. E.g. one CDR per thread >>> or by >>> implementing a CDR pool. >>> >>> Regards >>> Ralf >>> >>> Michael Crozier schrieb: >>> >>>> Hello, >>>> >>>> As outlined in the best practices document, I'm using >>>> ClassDescriptorResolver to load and cache mappings. I understand that >>>> Marshaller and Unmarshaller objects are not thread safe, but >>>> ClassDescriptorResolver has no mention of thread-safety. I am using >>>> this mechanism to load mappings from String objects and well as from >>> >>> >>> Files. >>> >>>> Is it thread-safe to share a single ClassDescriptorResolver instance >>>> between many threads, in which new marshalling objects are created >>> >>> >>> per-invocation? >>> >>>> Many thanks, >>>> >>>> Michael >>>> >>>> >>>> --------------------------------------------------------------------- >>>> 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 >> > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > 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
