Ok, I think I see a way how to do this: Input from the user: - desired context name - type of container (tomcat/jetty) if we can't determine this ourselfs - a .war file
Flow: - make sure all required data is in the request - save the uploaded file to a temporary location - tell the Assemble Mojo about the webapp and let it do its thing - tell the Deployment Mojo about the webapp and let it do its thing too. We supply that mojo with the deployer class selected by the user So we get these dependencies - maven-pluto-plugin (19KB) - pluto-util (36KB) - maven-core (133KB) - maven-artifact (77KB) - maven-plugin-api (10KB) - maven-project (103KB) Total: 378KB, just to get an idea.... I think this could work quite nice. Please tell me if you're okay with including all these maven dependencies or if you see any problems with the above idea. Patrick 2006/2/20, David H. DeWolf <[EMAIL PROTECTED]>: > On 2/19/06, Patrick Huber <[EMAIL PROTECTED]> wrote: > > > Hi, Patrick, > > > > For the web-service, we could do all the work in a servlet and use a > > > > portlet as thin frontend. Everything the Portlet does, is dispatching > > > > the request to the servlet. > > > > > > Having some sort of web service is a good idea, but i don't have much > > > experience on that... i will take a look at that if i have time. > > > > By web-service, I actually mean a simple servlet. Nothing that'd > > include soap and all that stuff. Just a simple servlet, to which a > > client can upload a war file. > > +1 -- me too -- we don't need to go crazy! :) > > > > -- "I love deadlines. I like the whooshing sound they make as they fly by." -- Douglas Adams
