Hi Frank, If you're using the CVS version of Castor, there is a "FieldHandlerFactory" interface which can be set in the introspector. This only works for introspection at present time, though I will eventually be enabling them in the Mapping as well.
To set a FieldHandlerFactory you can do the following: import org.exolab.castor.mapping.FieldHandlerFactory; import org.exolab.castor.xml.util.ClassDescriptorResolverImpl; import org.exolab.castor.xml.*; ClassDescriptorResolverImpl cdr = new ClassDescriptorResolverImpl(); cdr.getIntrospector().setFieldHandlerFactory(myFactory); ... myMarshaller.setResolver(cdr); ... myUnmarshaller.setResolver(cdr); Hope that helps, --Keith Frank Bingel wrote: > > Hi all, > > for the purpose of unmarshalling special fields we make use of > FieldHandlers. > Every time such a field is unmarshalled, a new instance of the associated > FieldHandler > is created (and candidate for garbage collection after done its work). > Because there > are a lot of documents to process, this leads to high garbage collector > activity. > It would be nice, if there was a way to control their instantiation, e.g. to > implement > a singleton pattern and thus reduce the garbage collector activity. > > Can anyone help me? > > Thank you very much! > > Frank > > -- > +++ GMX - die erste Adresse f�r Mail, Message, More +++ > Neu: Preissenkung f�r MMS und FreeMMS! http://www.gmx.net > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
