Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Sat, 11 Jun 2011 02:05:10 -0700 (PDT)
From: preben <pras@dr.dk>
To: users@camel.apache.org
Message-ID: <1307783110849-4478360.post@n5.nabble.com>
In-Reply-To: <BANLkTimbQGp0ELDcTB41f+yA-dcE2pzLfg@mail.gmail.com>
References: <1307644747404-4473771.post@n5.nabble.com>
 <BANLkTimbQGp0ELDcTB41f+yA-dcE2pzLfg@mail.gmail.com>
Subject: Re: Deployment unit versioninfo
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Year I guess you are right when we talk osgi, but if you use no osgi war
deployment in application containers it has no concept of wich version it is
running unless you deploy war with version info as part of the warfile name.
That would mean that you have to undeploy the old war and install the new
war.  

Typically thats not the case. You have the same warfile (name) redeployed
several times, but with different version info (in manifest or
pom.properties when building with Maven).

I was thinking this info from manifest or pom.properties + deployment unit
(warfilename) could be exposed as attributes on the CamelContext MBean (if
present of course).


--
View this message in context: http://camel.465427.n5.nabble.com/Deployment-unit-versioninfo-tp4473771p4478360.html
Sent from the Camel - Users mailing list archive at Nabble.com.