Hi All. I'm starting this thread to discuss about the $Subject. Here I describe the overview of the current model I'm working on.
SPI : *Runtime :* This provides the interface defining the model for the custom run-time implementation. [image: Inline image 2] Each runtime(Axis2/Tomcat etc.) will be registering an OSGI service corresponding to its functionalists, Ex : deployArtifacts(), undeployArtifacts(), startRuntime() etc. Artifact Deployer corresponding to specific runtime will consume this service to create and register its deployer service (serviceDeployer, webappDeployer) on the Deployment Engine. This custom deplyer must follow the instructions on [1]. There will be a service listener for runtime registration/un-registration events. This listener will update the RuntimeManager about the registered/unregistered services RuntimeManager will register another OSGI service which provide some management functionalists on the runtime services. Some uses of this service will be, - To control the start() of the available runtimes (Ex: delay until all transports are up on the server) - During server maintenance state we may need to control the states of the runtimes. Thoughts are welcome ......... [1] http://docs.wso2.org/display/Carbon500/Writing+your+own+Deployer Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188
<<Screenshot from 2014-01-15 20:44:27.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
