Hey,
Thanks for the reply. We moved away from this in the end and went for
object caching as a way to improve performance. It works well if your
JCR objects are never modified in the application.
Before we gave up on this approach I think I had something working, I'll
try and dig it out for reference
On 14/04/10 17:15, Woonsan Ko wrote:
Hi Toby,
I've just found that the lazy loading is not the default option, but you could set
"proxy" annotation property for @Bean or @Collection in the bean.
For example,
@Bean(jcrName="custom:content", proxy=true)
private Content content;
When you invoke getter method for the above property, it will retrieve the
target object if it hasn't be retrieved yet.
Also, you probably need to bring another dependency on asm:asm:1.5.3:jar
because jackrabbit ocm seems using cglib and transitively asm 1.5.3.
Regards,
Woonsan
----- Original Message ----
From: Toby O'Rourke<[email protected]>
To: "[email protected]"<[email protected]>
Sent: Fri, March 12, 2010 8:36:30 PM
Subject: OCM Lazy Loading?
Hi,
I see a bunch of classes in
org.apache.jackrabbit.ocm.manager.objectconverter.impl which suggest
that OCM supports Lazy Loading. Is this default behaviour or something I
need to configure? can some one give me a pointer where I should be
looking?
Thanks,
Toby.
