roedll: Thanks for your info I had checked Apache Sling but I didn't mentioned your previous conversations in forum. I've read the discussion <http://karaf.922171.n3.nabble.com/Task-scheduler-in-Karaf-td4028481.html> and also checked the KARAF-751 <https://issues.apache.org/jira/browse/KARAF-751> .
The overall idea behind reusing modified version of sling bundle for scheduler to prevent reinventing the wheel seems good. But I'm unable to summarize the debate about the SCR vs Blueprint in KARAF-751 comments. The SCR is part of OSGi spec and there is no reason not to use it. About a month ago, there was a similar discussion about having A Blueprint Free Karaf <http://karaf.922171.n3.nabble.com/A-Blueprint-Free-Karaf-td4030521.html> in forum. @iocanel had developed a version of Karaf by replacing Blueprint with Felix SCR. But currently, all the modules in Karaf have implemented using Blueprint, and I think it would be better to keep this design for now and if someday in future, project committee decided to replace Blueprint with SCR, all modules will be changed in one step (like what @iocanel did). JB: What's your opinion? Regards ----- E.Z.Moghaddam [email protected] -- View this message in context: http://karaf.922171.n3.nabble.com/Having-commands-for-scheduler-module-tp4030991p4031026.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
