take a look at the discussion on whether or not to set lazy-init="true" for SingletonBeans declared in Spring's IOC framework
http://www.javatx.cn/spring/reference/html_single/#beans-factory-lazy-init
If the load is small you might as well load everything up front
if the loading of the tables is extensive or the tables are seldom referenced you might want to consider holding-off (setting lazy-init="true") until those tables are actually referenced..
Anyone ?
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.
> Date: Sun, 8 Mar 2009 12:24:35 -0700
> From: glassfish_at_javadesktop.org
> To: users_at_glassfish.dev.java.net
> Subject: JPA: Preload data
>
> Hi!<br/>
> In a JPA application where all tables are created at application deployment, is there a "best practice" way of preloading the database with initial data, just after the application is deployed and the tables created, just before the application starts up?<br/>
> <br/>
> How would you solve this?<br/>
> <br/>
> Thanks,<br/>
> Mattias
> [Message sent by forum member 'nightzero' (nightzero)]
>
> http://forums.java.net/jive/thread.jspa?messageID=335753
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
_________________________________________________________________
Windows Live™ Groups: Create an online spot for your favorite groups to meet.
http://windowslive.com/online/groups?ocid=TXT_TAGLM_WL_groups_032009