Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <29735487.1163705259030.JavaMail.jira@brutus>
Date: Thu, 16 Nov 2006 11:27:39 -0800 (PST)
From: "Matt Hogstrom (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-557) smooth application
 upgrade/versioning
In-Reply-To: <653008596.1106868499859.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-557?page=all ]

Matt Hogstrom updated GERONIMO-557:
-----------------------------------

    Fix Version/s: Wish List
                       (was: 1.2)

> smooth application upgrade/versioning
> -------------------------------------
>
>                 Key: GERONIMO-557
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-557
>             Project: Geronimo
>          Issue Type: New Feature
>          Components: deployment, kernel
>            Reporter: David Jencks
>             Fix For: Wish List
>
>
> There have been several requests for the ability to change fairly fundamental bits of application configuration at runtime, such as which resource a resource-ref points to.  Currently the only way to do this is to redeploy the reconfigured application, and changing this would break a lot of our implementation and some of our philosophy.
> Perhaps a better way to approach this kind of problem is to version applications, and have a process for seamlessly switching between versions of an application.
> So, to change the target of a resource-ref, you'd configure a new "copy" of your app with the new target, deploy it, and undeploy the old version.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira