Looks good, thanks :) 2017-03-17 12:05 GMT+01:00 Greg Huber <[email protected]>: > Would this be enough information? > > https://issues.apache.org/jira/browse/WW-4762 > > Cheers Greg > > On 17 March 2017 at 07:16, Lukasz Lenart <[email protected]> wrote: > >> 2017-03-15 9:50 GMT+01:00 Greg Huber <[email protected]>: >> >>you can always implement your own >> >>LocalizedTextProvider and search in default bundles first and then >> >>fallback to searching class hierarchy. >> > >> > There seems alot going on in DefaultLocalizedTextProvider so I would >> rather >> > stay with the default and do the local modification. >> >> Right :) I hope with converting this class into a bean it will be >> possible to simplify things ;-) >> >> >>Something like getDefaultText() >> > >> > It would mean refractoring the code slightly, not sure what other users >> > would want, but I remember an email a while back on the same thing, ie >> only >> > using the default package of the class rather than all the interfaces >> etc. >> > Maybe class package, default then scan the interfaces (nifty thing)? >> >> It is possible, I mean adding another simplified implementation which >> only uses classes without scanning the class hierarchy. Could you >> register a ticket for that? >> >> >>Maybe I should prepare a small demo? >> > >> > Maybe give us an idea of how to use the bean. >> >> Sure, I will prepare one :) >> >> >> Regards >> -- >> Łukasz >> + 48 606 323 122 http://www.lenart.org.pl/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
