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
