Hi Dan Can you please post a complete sample object graph, as seen on the wire, and/or an object graph instance to be serialized by JAXB. As well as a corresponding sample after a (would be) max depth rule has been applied. We can then see if we can fix it generically at the JAXB (provider) layer by reacting to some system query like _maxdepth or say by executing an xpath-like query.
Would you be happy with limiting the response after the db query has been executed or would you prefer to make sure the db response already has been filtered as needed, by creating an appropriate db query ? If it's the former then I think we may have some space for solving this issue at the runtime layer by installing some system query handler reacting to queries like _maxdepth. Otherwise you'd likely need to come up with your own query language... cheers, Sergey Dan Check wrote: > > Hi all, > > I have a service that returns a list of objects (~75 in total). The full > graph of each object, as returned by hibernate, is about 100k. As a > result, > a listing of the full set runs about 7.5 MB. That, combined with the deep > retrieve, makes the listing incredibly expensive & slow. > > Is there an easy way that I can specify a max depth for these objects when > they're being sent over the wire? I'd like to be able to say that these > objects should go no deeper than three levels. I'd also be willing to say > that a certain part of the object is XMLTransient in this context, but > only > if I can say that it's not transient when the objects are retrieved > individually. I don't know what the best practice is here. > > I'm using the JAX-RS support, and JAXB for marshalling and unmarshalling. > > Thanks, > Dan > > > ----- > CONFIDENTIALITY NOTICE: The information contained in this message > may be privileged and confidential and protected from disclosure. > If the reader of this message is not the intended recipient, or > responsible for delivering it to the intended recipient, please > be advised that any distribution, dissemination, copying or other > transmission or use of the information contained in this message > or its enclosed attachments is strictly prohibited. Please > notify us immediately if you have received this message in error > by replying to the sender of the message and deleting it from > your computer. Thank you. > > > > -- View this message in context: http://www.nabble.com/Returning-Something-Less-Than-the-Full-Object-Graph-tp25089771p25095126.html Sent from the cxf-user mailing list archive at Nabble.com.
