In case you are still experiencing the same problem of xml data binding, I
suggest that you look at this article, which use xpath + vtd-xml to resolve
performance issues of xml data binding

http://onjava.com/pub/a/onjava/2007/09/07/schema-less-java-xml-data-binding-with-vtd-xml.html


Ralf Joachim-2 wrote:
> 
> Hi Rose,
> 
> final 1.3 has already been released at 10/Feb/2009. At the moment we are
> working toward 1.3.1.
> 
> Regards
> Ralf
> 
> rose_smith schrieb:
>> Hi
>>
>> Any idea when a stable 1.3 release will be availble? can't use RC in
>> production. 
>> Meantime is there a link to best practices/tricks for the doing the same
>> thing  ( load mapping only once) with the 1.2 release?
>>
>> -Rose
>>
>>
>> Werner Guttmann wrote:
>>   
>>> Hi,
>>>
>>> yes, create one instance of XMLContext only (setup period), and then use
>>> the create(Un)Marshaller() methods to create (Un)Marshaller instances as
>>> needed. In addition, have a look at the reference guide, especially at
>>> the section about performance tuning (best practise).
>>>
>>> Regards
>>> Werner
>>>
>>> picje wrote:
>>>     
>>>> Hello,
>>>>
>>>> I'm using castorl-1.3-xml and I would like to know what is the best
>>>> approach
>>>> to increase the performance. In fact for Marshalling/Unmarshalling I
>>>> use
>>>> this kind of code : 
>>>>
>>>>             
>>>> public RgSearchOutput1 parseRgSearchOutputControlXml(Reader xmlReader)
>>>> throws Exception {
>>>>         RgSearchOutput1 rgSearchOutput1 = null;
>>>>         try{       
>>>>             Mapping mapping = new Mapping();
>>>>             mapping.loadMapping(getRgSearchOutputXmlMapping());
>>>>             
>>>>            XMLContext context = new XMLContext();
>>>>                    context.addMapping(mapping);
>>>>                    
>>>>            Unmarshaller unmarshaller = context.createUnmarshaller();
>>>>                    unmarshaller.setValidation(false);
>>>>                    unmarshaller.setClass(RgSearchOutput1.class);
>>>>                    
>>>>            rgSearchOutput1 =
>>>> (RgSearchOutput1)unmarshaller.unmarshal(xmlReader);
>>>>                    
>>>>           
>>>>         }catch (Exception e){
>>>>             throw e;
>>>>         }
>>>>
>>>>         return rgSearchOutput1;
>>>> }    
>>>> My question is : Do I have to put in cache the instance of "XMLContext"
>>>> to
>>>> improve the performance ? What is the best approach when we are in a
>>>> Multithread environment?
>>>>
>>>> Thanks for your help.
>>>>
>>>>
>>>>       
>>> ---------------------------------------------------------------------
>>> 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
> 72127 Kusterdingen
> Germany
> 
> Tel.   +49 7071 3690 52
> Mobil: +49 173 9630135
> Fax    +49 7071 3690 98
> 
> Internet: www.syscon.eu
> E-Mail: [email protected]
> 
> Sitz der Gesellschaft: D-72127 Kusterdingen
> Registereintrag: Amtsgericht Stuttgart, HRB 382295
> Geschäftsleitung: Jens Joachim, Ralf Joachim
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Castor-XML-Performance.-tp22928731p27699656.html
Sent from the Castor - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to