Re: Pluto 1.1, Tomcat 5.5.12 and portlet deployment

[CDoremus]

I also find the duplication of pluto and testsuite deployments confusing and something we should do something about.
See below.


> On 11/3/05, Pollähne. Ullrich <[EMAIL PROTECTED]> wrote:
> Hi David,
>  
> thanks for the fast response.
>  
>  
> >Tomcat 5.5.9 works fine.
> Yes, tomcat.5.5.9 is really completely different. ;-)
> It creates pluto, pluto-portal, testsuite and pluto-testsuite. Is it
> planned to remove this duplicity?
>
> I haven't figured out a good solution for this yet.  If you have any
> ideas, chime in.  Here's my dilema:
>
> 1) I Iike the artifact names of pluto-testsuite, pluto-container,
> pluto-xxxx, etc. . .because generic artifact names can easily
> conflict with other projects.
>
> 2) In order to allow this but also allow simple context paths, pluto
> deploys the war and uses tomcat context configuration to bind the
> war to another context path.
>
> 3) Tomcat, by default, unpacks all wars, meaning that pluto-
> testsuite.war is unpacked to a directory named after it's context
> path --  /testsuite
>
> 4) Tomcat, also by default, auto deploys all wars in the webapps
> dir.  This results in pluto-testsuite.war being deployed to /pluto-testsuite
>
>
> So, the end result is what you're seeing.
>
> Another approach would be to point the context configuration a wars
> that are NOT in the webapps dir.  This may be the best approach but
> I'm not sure where we'd place the war.  Should we leave it in the
> target dir? move it to another subdir of tomcat? etc. . .

I think this is the best idea. We should create our own subdir (something like 'pluto-portal-wars')
and put our wars in that directory, pointing Tomcat to those files using the docBase attribute (Context element) in the pluto.xml and testsuite.xml configuration files.