Hi, can I take it that you have read
http://castor.org/reference/html/XML%20data%20binding.html#d0e2842 and understood the differences between using and not using XMLContext to create your (Un)Marshallers ? Regards Werner pravinab wrote: > Hi, > > I was using Castor 1.2 when reading the discussions around memory leaks and > single time initialization, i decided to move on to Castor 1.3. > Currently facing couple of issues which i have to resolve soon. > 1. I am using XMLContext to get an instance of UnMarshaller as specified in > the best practices. > Also, i am trying to use the XMLClassDescriptorResolver as mentioned in > one of the posts by Werner > Mapping mapping = new Mapping(); > mapping.loadMapping(...); > ClassDescriptorResolver classDescriptorResolver = > ClassDescriptorResolverFactory > .createClassDescriptorResolver(BindingType.XML); > MappingUnmarshaller mappingUnmarshaller = new MappingUnmarshaller(); > MappingLoader mappingLoader = mappingUnmarshaller.getMappingLoader( > mapping, BindingType.XML); > classDescriptorResolver.setMappingLoader(mappingLoader); > But i am getting a NullPointer in setMappingLoader(). > > 2) I have couple of big xmls which needs to be unmarshalled, but the same > takes around 5-7 secs to unmarshall..Any ways of improving the performance? > Just to bring to your notice, we do not map the entire xml to our data > objects..only required attributes from the xml are mapped to fields in Java > object through the mapping xml. > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
