It works exactly like that, though I used new configuration symbol for that.
Its value is "false" by default, and I set it to "true" only in my
ProductionModule.java
On Sun, May 12, 2013 at 11:33 AM, Kalle Korhonen wrote:
> Thanks Dmitry, that's an interesting solution. You could easily make it
Thanks Dmitry, that's an interesting solution. You could easily make it
eager load in production mode only that might be a fairly lucrative option
for many.
Kalle
On Sun, May 12, 2013 at 12:29 AM, Dmitry Gusev wrote:
> On Sat, May 11, 2013 at 1:20 PM, Dmitry Gusev >wrote:
>
> > This may work..
On Sat, May 11, 2013 at 1:20 PM, Dmitry Gusev wrote:
> This may work... but how would I know which services I need for that page?
> I want as much as possible.
>
> I did some research and found that there's no such global option.
>
> I did some reflection hack to call eagerLoad() on service defini
This may work... but how would I know which services I need for that page?
I want as much as possible.
I did some research and found that there's no such global option.
I did some reflection hack to call eagerLoad() on service definitions from
ServletContextAttributeListener, but that breaks some
Yeah, I know... I just don't want to eager load during development.
On Fri, May 10, 2013 at 4:27 PM, Lance Java wrote:
> You can annotate individual service builder methods in AppModule with
> @EagerLoad. There's also ServiceBindingOptions.eagerLoad() available for
> bind().
>
> Not sure if there
EagerLoad is a pain when developing. I my opinion you should kill two birds
with one stone. Setup a monitor page that includes the services you want to
eager load and point a website monitor at it. Then it takes the startup hit
instead of your users and you also know when the site is broken.
On F
You can annotate individual service builder methods in AppModule with
@EagerLoad. There's also ServiceBindingOptions.eagerLoad() available for
bind().
Not sure if there's a global option.
