you're right, Christian - the table implementation is simple enough that a full-blown service might be excessive for my immediate needs. moreover, importing packages is already a kind of service consumption. for better or worse, i might have gotten carried away with my enthusiasm for OSGi.
all the same, i wonder if Karaf's growing popularity could create new opportunities for third-party collaboration with the container. i'm still new around here, so take that with a grain of salt and forgive my imagination ^_^; btw, your table printer looks great - especially where it provides a DSL! can't wait to use it. ~ Reuben On Thu, Apr 5, 2012 at 14:26, Christian Schneider <[email protected]>wrote: > Why do you want to create a service for the table printer. You can create > it with "new". As service typically makes only sense when the > initialization is complicated or you want to hide the implementation. Both > is not the case for the tables. > On Thu, Apr 5, 2012 at 14:28, Christian Schneider <[email protected]> wrote: > I overlooked one aspect you mentioned. Usage for other projects. Here the > main concern is that you have to depend on the shell.console project. This > is the case for commands anyway. If this is an issue we might create a > separate bundle for the table functionality. On Thu, Apr 5, 2012 at 14:30, Christian Schneider <[email protected]>wrote: > I think it would make sense to user the karaf.util project for that. > Currently we just inline it into projects but we could also make it a > bundle. We could move the table functionality and other general tools > there. >
