Hi Manoj, OK. I was under the impression that the OSGi service registered by each runtime will be exposing all those methods and that it will be fully consumed by the Runtime Manager.
So, as you say the Deployment model has only changed a little bit, where each runtime that we come up with will register the Deployer in the Deployment Engine. So, if I understood you correctly, this OSGi service does not expose methods such as deployFoo() and undeployFoo(), but will only expose the startRuntime() and stopRuntime() methods. The rest of the methods will be internal/private to the Runtime. Thanks, Senaka. On Wed, Jan 15, 2014 at 11:00 PM, Manoj Kumara <[email protected]> wrote: > Hi Senaka, > > >> Alright. If so, we need to fix the interface of the OSGi Service >> registered by the Runtime, to have getDeployer() which (with return type >> Deployer) instead of deployArtifacts() and undeployArtifacts() instead of >> what you explained in the example. >> >> > Yes it can have getDeployer() and many more methods needed by runtime to > provide the intended functionalists. By deployArtifact() what I meant was > usage of runtime specific methods relevant to artifact deployment [ ex: for > Tomcat addWebapp() ]. These methods will be used by the custom deployer to > create the artifact deployer. > > > >> Each runtime(Axis2/Tomcat etc.) will be registering an OSGI service >> corresponding to its functionalists, >> >> Ex : deployArtifacts(), undeployArtifacts(), startRuntime() etc. >> >> The Runtime Manager can call the deploy and undeploy methods of the >> Deployer if that is available. If a deployer is not returned by the Runtime >> the Runtime Manager can simply not include it in its deployer list, and >> only invoke the start() and stop() methods. >> >> > The runtime will not be handling artifact the deployment and > un-deployment methods. These methods will be handled by the Deployment > Engine. If certain runtime need a deployer then it can register its > deployer on the Deployment Engine and it keep the control of > the deployment. Runtime is only interested on initializing and starting > its runtime. Registering the deployer is not coupled with the runtime. > > Thanks, > Manoj > -- *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
