>
> I found something interesting about how you've implemented
> your lazy loading of Resumes for a User.
>
> In UserManagerImpl.java you have this: -
>
> public UserForm convert(User user) throws Exception {
> userForm = new UserForm();
> // copy properties from user to form
> BeanUtils.copyProperties(userForm, user);
> ....
>
> I've confirmed that when BeanUtils is called, the User's
> Resumes and UserRoles are all retrieved from the DB (as I
> could see the SQL stmts printed out by Hibernate).
>
> I noticed this method is called in your ActionFilter. I don't
> think (at least in principle) that you want a whole gang of
> Resumes and UserRoles attached to a User in memory, right?
You're probably right. I can't think of how to solve this though -
except for removing the Hibernate mapping of parent -> child. I'm not
too worried about it as it's just a sample app. Any suggestions for
improvement are welcome.
Matt
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Struts-apps mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/struts-apps
