Hi all I had a look the admin portlet last week but I'll be pretty busy with all the exams the next two weeks and the preparations for my diploma thesis - so I won't have much time.
What I did so far: - write a portlet and servlet, calling a class named PlutoAdmin - an instance of PlutoAdmin is stored in the session for later requests - PlutoAdmin builds on a two-phase model just like the portlet's action/render - PlutoAdmin then does all the work, it's a controller/adapter to the assemble and deploy tasks Problems - the assemble and deploy tasks don't look really finished, if i had the time, i'd probably refactor them somewhat - my initial concept and the concept of the assemble and deploy tasks don't match so well but that can be fixed Notes - wherever something's left to do, there's a TODO comment - licence should be APL everywhere, if it's not, I have no problem with changing it to APL. The default in my eclipse is GPL. - It should all be pretty straightforward. nevertheless, I added some javadoc comments - pretty much everything that's missing is some glue between plutoadmin and the tasks and outputting the responses. If anyone would like to pick it up from here, download the source from here: http://www.swisstech.net/files/pluto-admin.tar.gz I'm sorry I don't have time to continue this, but I also don't want to stall so I'm giving you what I have so far... Patrick 2006/2/22, Elliot Metsger <[EMAIL PROTECTED]>: > Hi Patrick, > > I have a question below: > > Patrick Huber wrote: > > Ok, I think I see a way how to do this: > > <snip> > > > 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 > > After the deployment, can we test to make sure that the descriptor files > can be unmarshalled by the pluto portal up front, in time to notify the > uploader of the .war (instead of waiting for the "Error invoking > portlet" when the user loads the page). I will definitly get the exact > impl classes later but I'm waiting for coffee to brew then I'm off to > the salt mines, er work. > > Here's the situation I ran across when I was working with the > descriptors sub-project and the effort to create servlet 2.4 descriptors: > > With minor modifications descriptors subproject could successfully grok > an existing servlet 2.4 web.xml (that is, unmarshal it to a WebAppDD) > and successfully rewrite it with the Pluto servlet wrappers. Great! > BUT, the problem came when the pluto portal attempted to invoke my > portlet: the pluto portal was unable to unmarshal the Pluto-modifed web.xml. > > I will get exact stacktraces/classes later. That may help clarify - > > Thanks, > Elliot > -- "I love deadlines. I like the whooshing sound they make as they fly by." -- Douglas Adams
