• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

I18N x Refactoring

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I'm studying how to implement I18N in my application using Eclipse. I've seen a common approach is to have a message.properties file in each java source package.

However, with this approach, each time I rename a class or move it to other package, the message.properties files will stay outdated.

One solution is to internalize the class strings, refactor the class, and externalize the strings again. However, it seems not a good, fast process.

Is there a way to ease refactoring with I18N, changing the .properties files architecture or automating the changes that need to be made due to a refactor?

Thanks in advance,
Estevao Rohr.
 
Bartender
Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't think you can do this with out the box refactoring capabilities in eclipse, but someone in the IDE forum might have a better suggestion so I'll move this there. I wouldn't compromise your design just to make automatic refactoring work in a particular IDE.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic