Re: Struts 2.2.3 i18n properties not reloaded after redeployed

2011-06-20 Thread Maurizio Cucchiara
Don't use property reload in production environment: it could create
concurrency issues [1] (in addition to performance issues).
You should seriously re-consider if it is really necessary.

[1] https://issues.apache.org/jira/browse/WW-3461

On 20 June 2011 12:47, Vincent Lin  wrote:
> Hi Steven,
>
> I didn't restart the server.
> We are usint JBoss.
> We just copy the war file to deploy directory (the directory is
> similar to tomcat webapps)
>  and let Jboss to redeploy it.
>
> If the server is restarted, the i18 properties will be reloaded.
>
> Regards,
> Vincent
>
> On Mon, Jun 20, 2011 at 3:14 PM, Steven Yang  wrote:
>> i am not sure if there was any bug fix regarding i18n reload.
>> but can you describe how you "redeploy" your app?
>> do shutoff your server then deploy then start?
>> or do you just deploy without turning off anything?
>>
>> On Mon, Jun 20, 2011 at 1:55 PM, Vincent Lin wrote:
>>
>>> Hi,
>>>
>>> We migrated to Struts 2.2.3 recently.
>>> But we found that i18n properties are not reloaded after the web
>>> application redeployed.
>>> After setting struts.i18n.reload=true, it will be reloaded after
>>> redeployed.
>>> But page rendering speed is slow.
>>>
>>> Before 2.2.3, we were using Struts 2.0.11, the i18n properties will be
>>> reloaded after the web app is redeployed with
>>> struts.i18n.reload=false.
>>>
>>> Can we set any configuration to let i18n properties reloaded in 2.2.3
>>> without setting struts.i18n.reload=true?
>>> It seems to hurt performance a lot.
>>>
>>> Thanks!
>>> Vincent Lin
>>>
>>> -
>>> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
>>> For additional commands, e-mail: user-h...@struts.apache.org
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>



-- 
Maurizio Cucchiara

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: Struts 2.2.3 i18n properties not reloaded after redeployed

2011-06-20 Thread Vincent Lin
Hi Steven,

I didn't restart the server.
We are usint JBoss.
We just copy the war file to deploy directory (the directory is
similar to tomcat webapps)
 and let Jboss to redeploy it.

If the server is restarted, the i18 properties will be reloaded.

Regards,
Vincent

On Mon, Jun 20, 2011 at 3:14 PM, Steven Yang  wrote:
> i am not sure if there was any bug fix regarding i18n reload.
> but can you describe how you "redeploy" your app?
> do shutoff your server then deploy then start?
> or do you just deploy without turning off anything?
>
> On Mon, Jun 20, 2011 at 1:55 PM, Vincent Lin wrote:
>
>> Hi,
>>
>> We migrated to Struts 2.2.3 recently.
>> But we found that i18n properties are not reloaded after the web
>> application redeployed.
>> After setting struts.i18n.reload=true, it will be reloaded after
>> redeployed.
>> But page rendering speed is slow.
>>
>> Before 2.2.3, we were using Struts 2.0.11, the i18n properties will be
>> reloaded after the web app is redeployed with
>> struts.i18n.reload=false.
>>
>> Can we set any configuration to let i18n properties reloaded in 2.2.3
>> without setting struts.i18n.reload=true?
>> It seems to hurt performance a lot.
>>
>> Thanks!
>> Vincent Lin
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
>> For additional commands, e-mail: user-h...@struts.apache.org
>>
>>
>

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org



Re: Struts 2.2.3 i18n properties not reloaded after redeployed

2011-06-20 Thread Steven Yang
i am not sure if there was any bug fix regarding i18n reload.
but can you describe how you "redeploy" your app?
do shutoff your server then deploy then start?
or do you just deploy without turning off anything?

On Mon, Jun 20, 2011 at 1:55 PM, Vincent Lin wrote:

> Hi,
>
> We migrated to Struts 2.2.3 recently.
> But we found that i18n properties are not reloaded after the web
> application redeployed.
> After setting struts.i18n.reload=true, it will be reloaded after
> redeployed.
> But page rendering speed is slow.
>
> Before 2.2.3, we were using Struts 2.0.11, the i18n properties will be
> reloaded after the web app is redeployed with
> struts.i18n.reload=false.
>
> Can we set any configuration to let i18n properties reloaded in 2.2.3
> without setting struts.i18n.reload=true?
> It seems to hurt performance a lot.
>
> Thanks!
> Vincent Lin
>
> -
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>


Struts 2.2.3 i18n properties not reloaded after redeployed

2011-06-19 Thread Vincent Lin
Hi,

We migrated to Struts 2.2.3 recently.
But we found that i18n properties are not reloaded after the web
application redeployed.
After setting struts.i18n.reload=true, it will be reloaded after redeployed.
But page rendering speed is slow.

Before 2.2.3, we were using Struts 2.0.11, the i18n properties will be
reloaded after the web app is redeployed with
struts.i18n.reload=false.

Can we set any configuration to let i18n properties reloaded in 2.2.3
without setting struts.i18n.reload=true?
It seems to hurt performance a lot.

Thanks!
Vincent Lin

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org