Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of ole.ersoy@gmail.com designates
 209.85.212.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=Io6m3Ub7IisPxHMWTkF6U17Xe9a0PWha8+6VZQkkj+FlfYr2Lu3mJ3uRaVokixyBQQ
         nGxneH7Zb7cMhTiVLvmwbYsUNbDtFBeU2uXVlIz9Js3h2WwRSLmznZjWr3/fkutSyFhp
         2DoLP2l/llYBqAOJPthxKyucHsEUscpRChwEY=
Message-ID: <4DE6A208.40402@gmail.com>
Date: Wed, 01 Jun 2011 15:33:12 -0500
From: Ole Ersoy <ole.ersoy@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.1.12) Gecko/20100907 Fedora/3.0.7-1.fc12 Thunderbird/3.0.7
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Tomcat 7 Shared Class Loader Removed?
References: <4DE68E23.6050801@gmail.com>
 <99C8B2929B39C24493377AC7A121E21FAE71FF25D4@USEA-EXCH8.na.uis.unisys.com>
 <4DE69A0F.6020500@gmail.com>
 <99C8B2929B39C24493377AC7A121E21FAE71FF2745@USEA-EXCH8.na.uis.unisys.com>
In-Reply-To: 
 <99C8B2929B39C24493377AC7A121E21FAE71FF2745@USEA-EXCH8.na.uis.unisys.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Chuck,

Thank you.  I have some jars that I'm going to create an RPM for to help with provisioning.  Since I'm doing that I thought linking or putting them in the shared class loader repository might be smart, but perhaps not :).

Thanks again,
- Ole


On 06/01/2011 03:10 PM, Caldarale, Charles R wrote:
>> From: Ole Ersoy [mailto:ole.ersoy@gmail.com]
>> Subject: Re: Tomcat 7 Shared Class Loader Removed?
>
>> I was thinking about putting the jars in the shared repository,
>> rather than deploying them with the war.  Could you please help
>> me understand why this is bad?
>
> 1) You would have data sharing - probably inadvertent - across all the webapps.  Information can leak from one to another, which has serious integrity and security implications.
>
> 2) You would introduce versioning dependencies across all your webapp deployments, so if one copy of the webapp needed to be updated for a given client set, all would have to be updated simultaneously.
>
> 3) Redeployment or restart of a single webapp would be impossible.
>
> Other than saving a certain amount of disk and memory space (both of which are exceedingly cheap these days), what do you think you would gain?
>
>   - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org