Le samedi 2 juillet 2011 13:25:02, Niclas Hedhman a écrit : > *Sigh* --> Scheduler has a strange cross Service reference, between > > In ServiceActivation > @Service > private ScheduleRepository scheduleRepository; > > and > > In ScheduleRepository.Mixin > > @Service > private SchedulerService scheduler; > > effectively creating a cyclic dependency between the two.
Huh, I didn't notice this one. In ScheduleRepository the Scheduler service is used only to get its identity as every persisted Schedule use the corresponding Scheduler identity so you can have several independent Schedulers in the same application. At first sight I can't see how to solve this issue, any idea ? > So, I guess I come back to my original question; > > Is it a bug that the Service is available before activate() has been > executed? I didn't think about it so long but simply reading this sentence makes me feels it's wrong. My 0.000000002 cents :/ /Paul -- Paul Merlin - eskatos.github.com _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
