We're using RE to provide the Atom API in our jboss overlord s-ramp 
implementation.  Something we've run into is a performance problem 
iterating over certain Atom Feeds.  In some circumstances each Entry in 
the atom Feed can wrap an additional jaxb object.  We get access to this 
via Entry's getAnyOtherJAXBObject.

This all works great except that there is no JAXBContextFinder set on 
the Entry, so a new JAXBContext is created for each Entry.

I think the root of this problem is here:


Perhaps the finder should be set on the Entry either in all cases or 
maybe only when Entry:getAnyOtherElement() returns a non-null?


HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
Resteasy-users mailing list

Reply via email to