David H. DeWolf wrote:
1) Pluto should focus on the following 3 goals (in order and as stated
in it's mission):
- reference implementation
- easy portlet testing/development
- embeddable container for portal/webapp developers
<snip>
The question at hand (auto-deployment in pluto) is borderline
functionality to me. It specifically hits the second goal of pluto
(easy portlet testing/development), but could also be seen as enterprise
functionality.
I see it primarily as the second goal, but also as the third goal as
well; the idea is that embedders will get hot-deployment and assembly
for "free" by implementing relatively simple callbacks.
Assembly is really my focus. I'd like that to be abstracted away from
the portlet developer. Having portlet devs assembling wars is damaging
for the reasons at the bottom of [0].
Hot deployment is a natural consequence of assembly - if the "container"
is going to perform assembly at deployment time, it may as well put the
assembled war in a place where the servlet container will pick it up.
I'm totally open to how this is accomplished, if not in Pluto than in where?
[0] http://www.nabble.com/forum/ViewPost.jtp?post=11490584&framed=y
