Hi, I agree that iPojo is a very good component model and it will be hard to replace it. I think the closest you could come to replace it with would be a combination of Declarative Services (DS/SCR) and the new condition specification [0] - obviously depends on what you where actually doing with iPojo (for a simple @Controller it might be enough to use conditions).
That said, let me point out: there is no reason iPojo couldn't still be developed - we just lack somebody to work on it for the time being. If you (and/or others you know) want to continue to develop it that certainly could be a way forward as well. regards, Karl [0] http://docs.osgi.org/specification/osgi.core/8.0.0/service.condition.html#service.condition On Tue, Sep 7, 2021 at 10:39 AM Bengt Rodehav <[email protected]> wrote: > > I have noticed that iPojo is not supported any more. That is unfortunate > for us since we have built a lot of our functionality on iPojo. It's > actually the best component model I have seen so far. > > We need to move on to something else then. What would you suggest? What > alternative is closest to iPojo in functionality? > > The big difference for us has been the @Controller annotation. With this we > have a system where we enable/disable services using configurations. I > really need some way to achieve the same but with another model than iPojo. > I would appreciate any suggestions. > > /Bengt -- Karl Pauls [email protected]
