Hi Angel ; Yes , you can easily do that (in fact I have done that.) , you can write a service to deploy and unDeploy other services. Then you can send the service you want to deploy as a MTOM attachment. Then the service can get the attachment and deploy the way he like - He might drop the attachment into service directory as an .aar file - Or he can make the attachment into a service
Thanks Deepal > Hi, > > Yes that is fine. A service will also work and I actually like this > more than the servlet. The issue I was thinking about in that case is > whether it would be possible to obtain the deployengine instance > created by the AxisServlet (not directly). Normally a servlet would > obtain that through the Servlet context. But i am sure there would be > a way to do this easily with a web service as well. Thanks for the > feedback. > > Regards, > Angel > > On 2/9/07, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > >> Hi Angel, >> >> First of all, welcome to the dev community and I look forward to seeing >> more contributons from you! >> >> I'm +1 in having a remote deployment capability. However, I can't see >> why we don't write a simple Web service with deploy()/undeploy() etc. >> methods, use MTOM/XOP for sending the aar files and use the REST/POX >> stuff to get a clean HTTP binding for it. That way we don't need to >> write another servlet or anthing- you just write a service and the user >> deploys it if they want remote deployment. Of course if the user is >> smart they'd secure that service a little bit. >> >> The other advantage is that this'll work on all transports .. one could >> envision sending an email to the service to deploy stuff. On an IM over >> XMPP. >> >> Sanjiva. >> >> On Fri, 2007-02-09 at 16:17 +0200, Angel Todorov wrote: >> > Hi All, >> > >> > I think it would be good to have the following functionality in Axis2, >> > with respect to deployment and administration: >> > >> > - remote deployment servlet -> receives HTTP requests for >> > deploy/undeployment of services (can also have listing of services as >> > a helper). Deployment archives can be sent using multipart. >> > Authentication should be supported as well. The communication protocol >> > would be minimal in terms of abundance of info (no HTML ,etc.). >> > >> > - remote admin servlet -> same as the above but for administration, >> > starting and stopping of services and modules, health monitoring. >> > >> > The above can extend from AxisServlet on one hand, and the >> AbstractAgent. >> > >> > These also require a deploy client API as well. The implementation of >> > that can be integrated in an eclipse plugin, as a standalone console >> > application, or in any way, in general. >> > >> > I have started doing the above and would like to contribute it at some >> > point. Your feedback is appreciated. Thanks. >> > >> > Best Regards, >> > Angel >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> -- >> Sanjiva Weerawarana, Ph.D. >> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ >> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ >> Director; Open Source Initiative; http://www.opensource.org/ >> Member; Apache Software Foundation; http://www.apache.org/ >> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
