Hi all, I have a few questions / comments on the Aries Application API. Specifically, about AriesApplicationManager and AriesApplicationContextManager API.
The application-management module provides a default implementation for the AriesApplicationManager API while the application-runtime module provides an example implementation of the AriesApplicationContextManager API. It is expected (as indicated by JavaDoc) that different server runtimes will provide their own implementations of the AriesApplicationContextManager API. So it seems to me like the AriesApplicationContextManager is more of a SPI - something that user shouldn't/wouldn't normally use. If so, the user would only interact with the AriesApplicationManager API to perform application operations. If that's true then the AriesApplicationManager is missing methods for getting all AriesApplicationContexts or finding one by name. And at the same time the AriesApplicationContextManager would probably need to be completely reworked. For example to be named AriesApplicationManagerProvider and have corresponding install/uninstall/getContexts/findContext operations. Or maybe we should just get rid off the AriesApplicationContextManager completely and let folks implement the AriesApplicationManager API directly? Btw, by 'user' I meant some code that uses these API to perform some application operations. For example, in my case, I would like to have some osgi shell commands that use these API to install/uninstall/start/stop applications. Jarek
