You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Sorin Silaghi <so...@gmail.com> on 2011/03/23 09:18:17 UTC
Ensuring SA update in ServiceMix 4.3.0 for testing
Hello,
I wrote a bash script for testing our ServiceMix SA but since
the 4.3.0 release it looks like the SA doesn't always update as I
expect it to. I presume there's some caching going on or something.
Here's how the script works: it makes sure the SMX instance is
stopped, it copies the new SA and then starts SMX.
My question is what do I need to do to be absolutely sure the
SA gets updated when I deploy a new version? Is there any directory I
could delete? Should I keep SMX running while updating the SA?
Sorin.
Re: Ensuring SA update in ServiceMix 4.3.0 for testing
Posted by Freeman Fang <fr...@gmail.com>.
On 2011-3-23, at 下午5:50, Sorin Silaghi wrote:
> Hi,
>
>
> Since this is a test environment I'd rather not do a hot
> deploy. Also I can't delete the data directory since there's features
> that I need to have installed, like camel-ftp for example. Or is there
> any (easy) way I could install those features from my script ?
>
Hi,
You can in your script to start a client console which enable you
execute a command like features:install camel-ftp to install any
features you want.
Freeman
>
> Sorin.
>
> On Wed, Mar 23, 2011 at 11:42 AM, Freeman Fang
> <fr...@gmail.com> wrote:
>> Hi,
>>
>> My comment inline
>> On 2011-3-23, at 下午4:18, Sorin Silaghi wrote:
>>
>>> Hello,
>>>
>>>
>>> I wrote a bash script for testing our ServiceMix SA but since
>>> the 4.3.0 release it looks like the SA doesn't always update as I
>>> expect it to. I presume there's some caching going on or something.
>>>
>>> Here's how the script works: it makes sure the SMX instance is
>>> stopped, it copies the new SA and then starts SMX.
>>
>> I assume you copy the SA.zip(not the .jar) to the SMX4_HOME/deploy
>> folder.
>>>
>>> My question is what do I need to do to be absolutely sure the
>>> SA gets updated when I deploy a new version? Is there any
>>> directory I
>>> could delete? Should I keep SMX running while updating the SA?
>>
>> You needn't stop the container, you can do hot redeploy with
>> container up.
>> Also you can remove SMX4_HOME/data folder and then start container
>> again
>> which ensure everything new could be picked up.
>>
>> Freeman
>>>
>>>
>>> Sorin.
>>
>>
>> --
>> Freeman Fang
>>
>> ------------------------
>>
>> FuseSource: http://fusesource.com
>> blog: http://freemanfang.blogspot.com
>> twitter: http://twitter.com/freemanfang
>> Apache Servicemix:http://servicemix.apache.org
>> Apache Cxf: http://cxf.apache.org
>> Apache Karaf: http://karaf.apache.org
>> Apache Felix: http://felix.apache.org
>>
>>
--
Freeman Fang
------------------------
FuseSource: http://fusesource.com
blog: http://freemanfang.blogspot.com
twitter: http://twitter.com/freemanfang
Apache Servicemix:http://servicemix.apache.org
Apache Cxf: http://cxf.apache.org
Apache Karaf: http://karaf.apache.org
Apache Felix: http://felix.apache.org
Re: Ensuring SA update in ServiceMix 4.3.0 for testing
Posted by Sorin Silaghi <so...@gmail.com>.
Hi,
Since this is a test environment I'd rather not do a hot
deploy. Also I can't delete the data directory since there's features
that I need to have installed, like camel-ftp for example. Or is there
any (easy) way I could install those features from my script ?
Sorin.
On Wed, Mar 23, 2011 at 11:42 AM, Freeman Fang <fr...@gmail.com> wrote:
> Hi,
>
> My comment inline
> On 2011-3-23, at 下午4:18, Sorin Silaghi wrote:
>
>> Hello,
>>
>>
>> I wrote a bash script for testing our ServiceMix SA but since
>> the 4.3.0 release it looks like the SA doesn't always update as I
>> expect it to. I presume there's some caching going on or something.
>>
>> Here's how the script works: it makes sure the SMX instance is
>> stopped, it copies the new SA and then starts SMX.
>
> I assume you copy the SA.zip(not the .jar) to the SMX4_HOME/deploy folder.
>>
>> My question is what do I need to do to be absolutely sure the
>> SA gets updated when I deploy a new version? Is there any directory I
>> could delete? Should I keep SMX running while updating the SA?
>
> You needn't stop the container, you can do hot redeploy with container up.
> Also you can remove SMX4_HOME/data folder and then start container again
> which ensure everything new could be picked up.
>
> Freeman
>>
>>
>> Sorin.
>
>
> --
> Freeman Fang
>
> ------------------------
>
> FuseSource: http://fusesource.com
> blog: http://freemanfang.blogspot.com
> twitter: http://twitter.com/freemanfang
> Apache Servicemix:http://servicemix.apache.org
> Apache Cxf: http://cxf.apache.org
> Apache Karaf: http://karaf.apache.org
> Apache Felix: http://felix.apache.org
>
>
Re: Ensuring SA update in ServiceMix 4.3.0 for testing
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
My comment inline
On 2011-3-23, at 下午4:18, Sorin Silaghi wrote:
> Hello,
>
>
> I wrote a bash script for testing our ServiceMix SA but since
> the 4.3.0 release it looks like the SA doesn't always update as I
> expect it to. I presume there's some caching going on or something.
>
> Here's how the script works: it makes sure the SMX instance is
> stopped, it copies the new SA and then starts SMX.
I assume you copy the SA.zip(not the .jar) to the SMX4_HOME/deploy
folder.
>
> My question is what do I need to do to be absolutely sure the
> SA gets updated when I deploy a new version? Is there any directory I
> could delete? Should I keep SMX running while updating the SA?
You needn't stop the container, you can do hot redeploy with container
up.
Also you can remove SMX4_HOME/data folder and then start container
again which ensure everything new could be picked up.
Freeman
>
>
> Sorin.
--
Freeman Fang
------------------------
FuseSource: http://fusesource.com
blog: http://freemanfang.blogspot.com
twitter: http://twitter.com/freemanfang
Apache Servicemix:http://servicemix.apache.org
Apache Cxf: http://cxf.apache.org
Apache Karaf: http://karaf.apache.org
Apache Felix: http://felix.apache.org