This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I've been revising the source code in my SCJD project again, and was thinking about externalizing string. Hmmm... does it make sense for that project, isn't it overkill?? Or maybe it would be a nice thing to mention in choices.txt in a kind of "future improvements" topic?? What do you think??
What do you mean by "externalizing Strings"? Are you talking about putting your Strings into a bundle for internationalization? Or something else?
(If you are looking at internationalization, I think it is really nice, but beyond specifications - so you wont get extra marks for it. But it would be good to mention that you thought of it in your design choices document.
Since there is a database-related requirement about "8-bit US-ASCII", I am not certain that it truly makes sense to externalize strings. If the requirements specified ISO-Latin, it might be a different story...
Joined: Jan 02, 2004
Ok, this is my fault I was not specific enough. By externalizing strings I mean what Andrew said - putting the strings that are normally hardcoded into a bundle that is located in one place and it's easily replaceable with another set. This is just a temptation, and I know I won't be given extra score for that, so I think this is one of this kind of temptations I will resist
BTW. I thought "externalizing strings" is quite common notion, but hmmm... maybe I'm to much tied to the eclipse IDE that provides that facility.