Elaborate explanation of managing boilerplate text (e.g. titles, button labels, prompt, error messages, tool tips) in JSF applications. This includes more advanced locale requirements, like certain text that needs to be different when shown to junior and senior users.

Here's a nice diagram with an overview of what activities are needed to create a website, from idea to support and everything in between.

Always annoyed that you have to manually close a resource like InputStreams, Connections etc? And that the first exception might be surpressed by the second in the finally block? Here's a suggested solution: the Automatic Resource Management pattern by Joshua Bloch.

No comments:

About Me

I'm a professional software designer/architect/developer with over 20 years of experience. For many years I've been a Technical Team Lead for complex ICT projects. My main area of focus is Java application architectures and related challenges (scalability, performance etcetera), but I'm interested in any software application architecture. Currently Android has got a lot of my attention. I will be posting lessons learned, and lessons that I'll be learning during the coming years :-)