Re: LocaleProvder not unique

thank you, will look at it and report on dev On Wed, Mar 15, 2017, at 09:23, Lukasz Lenart wrote: > Christian > > Change is here https://github.com/apache/struts/pull/122 > > 2017-03-14 10:16 GMT+01:00 Lukasz Lenart : > > Feel free to register an issue with your case >

Re: LocaleProvder not unique

Christian Change is here https://github.com/apache/struts/pull/122 2017-03-14 10:16 GMT+01:00 Lukasz Lenart : > Feel free to register an issue with your case > > 2017-03-14 10:13 GMT+01:00 Christian Grobmeier : >> Yes, actually I think you are

Re: LocaleProvder not unique

Feel free to register an issue with your case 2017-03-14 10:13 GMT+01:00 Christian Grobmeier : > Yes, actually I think you are right: LocaleProvider and TextProvider > have both the same issue. It's just popping up for me with > LocaleProvider first, but TextProvider will

Re: LocaleProvder not unique

Yes, actually I think you are right: LocaleProvider and TextProvider have both the same issue. It's just popping up for me with LocaleProvider first, but TextProvider will surely follow. I try to read more dev list again, so feel free to ping me whenever you want me to test/help On Tue, Mar 14,

Re: LocaleProvder not unique

https://issues.apache.org/jira/browse/WW-4756 I know that this is for TextProvider but the same approach I can use for LocaleProvider 2017-03-14 6:53 GMT+01:00 Lukasz Lenart : > 2017-03-13 21:51 GMT+01:00 Christian Grobmeier : >> OK, using component

Re: LocaleProvder not unique

2017-03-13 21:51 GMT+01:00 Christian Grobmeier : > OK, using component scan i had success with using DefaultLocaleProvider > as default in my applicationContext.xml: > class="com.opensymphony.xwork2.DefaultLocaleProvider" primary="true" /> > > (mind the primary) > > So far

Re: LocaleProvder not unique

OK, using component scan i had success with using DefaultLocaleProvider as default in my applicationContext.xml: (mind the primary) So far it makes halfway sense to me. A few tests fail still because they access getText and do no receive a context. Digging into this On Mon, Mar 13, 2017, at

Re: LocaleProvder not unique

On Mon, Mar 13, 2017, at 19:08, Lukasz Lenart wrote: > 2017-03-13 19:03 GMT+01:00 Christian Grobmeier : > > Wether @Service was right or not, I need to somehow tell Spring how to > > find my beans (i.e. @Component). > > I can understand Springs confusion, when it realizes

Re: LocaleProvder not unique

2017-03-13 19:03 GMT+01:00 Christian Grobmeier : > Sorry, one more thing. > > With removing the @Service annotation I delegated the instantiation of > the Actions to Struts as the Spring component scanner will not find my > Bean no more. Struts - to my knowledge - will

Re: LocaleProvder not unique

Sorry, one more thing. With removing the @Service annotation I delegated the instantiation of the Actions to Struts as the Spring component scanner will not find my Bean no more. Struts - to my knowledge - will somehow create the bean using Spring too. The problem to use the applicationContext

Re: LocaleProvder not unique

On Mon, Mar 13, 2017, at 18:26, Lukasz Lenart wrote: > 2017-03-13 17:55 GMT+01:00 Christian Grobmeier : > > Removing @Service helped. In addition I had to remove the remaining > > Actions from applicationContext.xml (I am in the middle of a > > transition). > > > > It's

Re: LocaleProvder not unique

2017-03-13 17:55 GMT+01:00 Christian Grobmeier : > Removing @Service helped. In addition I had to remove the remaining > Actions from applicationContext.xml (I am in the middle of a > transition). > > It's kind a weird, because it worked with the previous version of > Struts.

Re: LocaleProvder not unique

Removing @Service helped. In addition I had to remove the remaining Actions from applicationContext.xml (I am in the middle of a transition). It's kind a weird, because it worked with the previous version of Struts. Was there a change in the injection behavior? I am glad I know about @Service

Re: LocaleProvder not unique

On Mon, Mar 13, 2017, at 16:31, Lukasz Lenart wrote: > 2017-03-13 16:25 GMT+01:00 Christian Grobmeier : > > @Service > > @Scope(value = ConfigurableBeanFactory.SCOPE_PROTOTYPE) > > public class EmptyAction extends AbstractAction { > > Looks like you have turned each action

Re: LocaleProvder not unique

2017-03-13 16:25 GMT+01:00 Christian Grobmeier : > Sure. > > I use annotations, i. e.: > > @Service > @Scope(value = ConfigurableBeanFactory.SCOPE_PROTOTYPE) > public class EmptyAction extends AbstractAction { Looks like you have turned each action in a bean. Can you drop

Re: LocaleProvder not unique

Sure. I use annotations, i. e.: @Service @Scope(value = ConfigurableBeanFactory.SCOPE_PROTOTYPE) public class EmptyAction extends AbstractAction { (AbstractAction extends ActionSupport) In applicationContext: I have used my own stack with: - The action config is still xml. like:

Re: LocaleProvder not unique

2017-03-13 16:02 GMT+01:00 Christian Grobmeier : > Hello all, > > I trying to upgrade my Struts app from 2.5.1 to 2.5.10.1. > > I saw there are some changes in I18nInterceptor like that: >