Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Soliciting Ideas for Dealing with Initial Entity Manager Creation Lag

Thanks for the ideas Shaun. One problem I see with just making the
plugin with the jpa stuff eager is that once you have 8 different
plugins loading EO's from 10 different schemas you're loading up a lot
of stuff you don't need to.  Really at it's core this isn't an
EclipseLink problem, but just the nature of the beast.  The only happy
middle ground I could see would be to not go full eager, but not full
lazy either -- so try to guess that a user is going to do something.
For example, if they initialize a view that will probably open an
editor that needs EclipseLink, load in the background during that

Thanks for the reply, looks like we're on pretty much the same page
and dealing with it is just part of the normal problem you have with
lazy vs eager loading.


On Thu, May 1, 2008 at 9:36 AM, Shaun Smith <shaun.smith@xxxxxxxxxx> wrote:
>  How about refactoring your domain model and persistence related artifacts
> (like persistence.xml) into a separate plugin that is eagerly loaded. The
> rest of your app (editors, etc.) could still be lazy?  In your eager plugin
> I'd create an EntityManager and then close it just to force the processing
> of your entities (we need to examine the annotations and any mapping files)
> and creation of your connection pools.  Also, you will probably want to dial
> down the number of connections in your pools to a couple.  This has a big
> impact on startup time.  I think I was doing this in the RCP example in the
> OSGi POC SVN branch?
>      Shaun
> --
>  Shaun Smith | Principal Product Manager, TopLink | +1.905.502.3094
>  Oracle Fusion Middleware
>  110 Matheson Boulevard West, Suite 100
>  Mississauga, Ontario, Canada L5R 3P4
> _______________________________________________
>  eclipselink-users mailing list
>  eclipselink-users@xxxxxxxxxxx


Back to the top