I think the LifecycleManager is the way I see the things. But unfortunately Pearry push the service in the OSGi registry during the construction process and it is not the way I would like to see it working. So I have 2 options: 1. rewrite part of peaberry workflow. 2. use the other approach based on the Guice SPI and event raised during object construction.
Romain. 2012/9/4 Jan Galinski <[email protected]> > I just blogged my PostConstructModule. It can be used just like >>> "install(PostConstructModule.INSTANCE)" and you have Postconstruct >>> behaviour. >> >> > The post is in german, but the code should be readable .... > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-guice/-/9Sutlr1cvdQJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
