[EMAIL PROTECTED] wrote : Say I've got a service that has some dependencies
that need to be injected before it can start up.
| My first question is, when do the dependencies get injected, with relation
to the service lifecycle methods?
|
It again depends where you want to inject. ;-)
OK, then I think I'm confused - how does the controller state lifecycle relate
to the service lifecycle? The service lifecycle seems to define four
trasitions - create, start, stop, and destory. But the controller can be in 8
different states.
View the original post :
[EMAIL PROTECTED] wrote : OK, then I think I'm confused - how does the
controller state lifecycle relate to the service lifecycle? The service
lifecycle seems to define four trasitions - create, start, stop, and destory.
But the controller can be in 8 different states.
We have more fine
alesj wrote : We have more fine grained states than the usual lifecycles. ;-)
| And what you call stop and destroy are respectively start and create on the
way 'back', at uninstall.
Yeah, I figured out that much. So the lifecycle methods described in
http://tinyurl.com/2qlxsq (13.3 of the
Which three states you have in mind?
I'll do a simple explanation of what each state does, or better, what each
action corresponding to state does:
In install phase:
NOT_INSTALLED - initial state
PRE_INSTALL - initialize scoped metadata, check for hierarchy of Controllers
DESCRIBED - add aop
Ah - I get it! I was confused after all. And in fact, re-reading the
lifecycle chapter, you do explain this a bit.
OK, this totally makes sense now. Sorry for the dumb questions.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4131588#4131588
Reply to the
