this shared-build war sounds like you *might* want a base servlet webapp
(portal) servicing n number of portals
checkout liferay, hippo and jetspeed (portal management systems) for those
specific implementations...
follow konstantins advice to successfully deploy this webapp under tomcat
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Tue, 22 Feb 2011 10:56:30 -0500
> From: shev...@homeport.org
> To: users@tomcat.apache.org
> CC: knst.koli...@gmail.com
> Subject: Re: 400 Errors while trying to deploy manager app.
>
> On 2/22/2011 3:37 AM, Konstantin Kolinko wrote:
> > Two steps:
> > 1. Remove path and docBase from the file.
> > 2. Rename the context file into "META-INF/context.xml" (exact name --
> > case of characters does matter!) and add it into your war file. (That
> > is easy with Ant, or with `jar -uf`, I do not know about jenkins).
> > That file will be used by Tomcat when you deploy your application.
> > See "Context" page in the configuration reference for more details.
>
> Sure, I understand that part of how Context works, the problem is this
> is a shared-build war file, and the Parameters are used to tell the
> deployed war file where to store it's config file and log configuration.
> So I can't embed it into the .war file.
>
> The goal is to have a mvn tomcat:deploy punch a war file via the manager
> into a running tomcat server, and having it's context there have
> Parameters associated with it. I think this might be impossible since
> tomcat-deploy makes up it's own context upon deployment :-/
>
> -d
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
