On Thu, 3 Apr 2003 [EMAIL PROTECTED] wrote:
> Date: Thu, 3 Apr 2003 22:15:10 +0200
> From: [EMAIL PROTECTED]
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: RE: partially updating a WAR file using manager app??
Hi Yoav/Craig,
I'll take a look at the entry points you gave me - maybe I'll find my way
through them.
Of course I'll keep you posted if I get useful results...
However, I still think it's a fundamental lack of the WAR approach not
being able to incrementally add functionality.
I originally com
On Thu, 3 Apr 2003 [EMAIL PROTECTED] wrote:
> Date: Thu, 3 Apr 2003 17:33:06 +0200
> From: [EMAIL PROTECTED]
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: RE: partially updating a WAR file using manag
Howdy,
>BTW - Let's say portability here is not my primary goal here.
That's pretty much a conversation stopper for me ;) I'm not interested
in container-specific solutions. Especially ones that are unlikely to
work even in the next major release of this container (i.e. tomcat 5.x).
>What abo
se respond to
"Tomcat Users List" <[EMAIL PROTECTED]>
To
"Tomcat Users List" <[EMAIL PROTECTED]>
cc
Subject
RE: partially updating a WAR file using manager app??
Howdy,
By definition, a war file is a complete application. Even if you could
get around this limitat
Howdy,
>I understand this definition, but am not a 100% satisfied with it.
>Hmm. Maybe here the J2EE specification of Sun is not sufficient.
Perhaps. If you keep pushing on this, with an organized proposal, then
people will listen eventually ;) It is an open standard after all.
>Shouldn't the
PROTECTED]>
To
"Tomcat Users List" <[EMAIL PROTECTED]>
cc
Subject
RE: partially updating a WAR file using manager app??
Howdy,
By definition, a war file is a complete application. Even if you could
get around this limitation by somehow finding a way to deploy one JSP
Howdy,
By definition, a war file is a complete application. Even if you could
get around this limitation by somehow finding a way to deploy one JSP
outside the war file, your solution wouldn't be portable. Just
repackage and redeploy the war. Both of these tasks should be quick and
easy as they
