On 8/22/07, Steve S <[EMAIL PROTECTED]> wrote: > Keeping the session open and turning off lazy loading both have the same > undesirable side effect of loading the entire object graph before returning > a result. This can result in a very large amount of data being returned. > What I was really hoping for was a way to change the way the XML was > generated so that it took Hibernate Collections into mind so that I can > check if it is initialized or not before descending into the collection. >
<snip> Lazy loading hibernate AFAIK doesn't work across JVM's so I'm failing to see a use case for it in web services. Using hibernate interceptors or perhaps eventing would be one way to know if the collection was populated - but that's pretty off topic for this list. There are ways to prevent axiom from loading everything in memory via streaming it, while still getting the graph into the xml. Search the list if interested as the topic comes up sometimes. HTH, Robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
