> Date: Tue, 17 Feb 2015 21:48:28 +0100
> From: Maria Elena <ringmeiste...@gmail.com>
> Subject: Re: [Resin-interest] [Resin] Locking jar Oracle
> To: ML Caucho Resin <email@example.com>
> Content-Type: text/plain; charset="utf-8"
> On Tue, Feb 17, 2015 at 8:41 PM, Nam Nguyen <n...@caucho.com> wrote:
>> Date: Tue, 17 Feb 2015 09:59:43 +0100
>>> From: Maria Elena <ringmeiste...@gmail.com>
>>> Subject: [Resin-interest] [Resin] Locking jar Oracle
>>> To: ML Caucho Resin <firstname.lastname@example.org>
>>> Content-Type: text/plain; charset="utf-8"
>>> I am using Resin 3.1.9 (too old, I know) and I am experiencing problems
>>> with Oracle jars (I am swtiching between Oracle11 and Oracle12).
>>> Tomcat has the antiJARlocking attribute; there is something similar in
>>> Thanks and regards.
>> Hi Maria,
>> It looks like all that Tomcat's antiJARlocking does is make a new copy of
>> the webapps directory on redeploys. Is that the feature you wanted?
>> Resin doesn't have something like that. But you can deploy multiple
>> versions of a webapp, effectively accomplishing the same thing.
>> -- Nam
> Hi Nam,
> thanks for your reply!
> What do you mean with "you can deploy multiple versions of a webapp"?
I'm not entirely sure of the capabilities of 3.1.9, but I think it
supports versioning at least. See:
<web-app-deploy ... versioning="true"/>
Suppose your WAR file is named myapp.war. If you want versioning, then
you'll need to have some sort of numbering convention. The following
You should deploy myapp-1.0.war first, not myapp.war. Then upgrade as
you see fit. When the sessions for an old version expires, Resin will
undeploy the old version.
resin-interest mailing list