PostConstruct on JBoss 6 M2 not working

[hbraun.myownwastebin.gmail.com]

My beans deploy correctly on JBoss 6 M2, but neither @PostConstruct not @PreDestroy are invoked. I would expect them to reflect the deployment lifecycle, no? I.e. upon removal of a beans jar from server/default/deploy the pre-destroy callback should be invoked, no?

[nickarls]

Show us some code.

Especially the usage part so we see that it's actually instantiated and not only proxied...

[hbraun.myownwastebin.gmail.com]

Especially the usage part so we see that it's actually instantiated and not only proxied...

your are right. the proxy is created and upon invocation everything works as expected. My bad.

[hbraun.myownwastebin.gmail.com]

BTW, is there a way to force creation of @ApplicationScope'd instances at the time a proxy is requested?

[nickarls]

Well proxies are constructed in a non-extensible place so it's a bit tricky, besides they are all created at startup. Of course it shouldn't be that difficult to write an extension that observes AfterDeploymentValidation and warms up the application context for beans with a @Startup annotation or something like that.

[hbraun.myownwastebin.gmail.com]

Yeah, agree. It's an edge case I am asking for. I mean that's the reason why we have proxies in the first place. Let's see how far I can take it. Thanks for your help.

[pmuir]

Heiko Braun wrote on May 10, 2010 15:43:


Yeah, agree. It's an edge case I am asking for. I mean that's the reason why we have proxies in the first place. Let's see how far I can take it. Thanks for your help.

In general, you can't rely on behavior like this - the container is free to lazily or eagerly instantiate beans in any situation. Best approach if you need to mimic eager-instantiation is to call a method on the instantiated bean.