If you are working on different projects locally then you might want to access them with the project name in the browser without providing the localhost prefixing it, just like how a production environment URL would look like. Apache is an amazing web server that can front end a web application irrespective of technology (except for .Net as far as I know). Apache can be configured to work with other application servers and the request routed to them appropriately. But most of the scripting language based web application such as PHP can work directly from Apache using the appropriate module plugin. Setting up Apache on your local development environment to configure and host the projects locally will provide an environment that resembles production and will also help learn Apache. Here is a good article “Setting Up Multiple Apache Local Web Sites On Your Computer” that provides details of how to do it.

How do you customize a feature? Customizations that will involve user initiated feature? While this does not mean that a user can create a feature out of the air but under the context of the application’s domain features could dynamically adopt to a user’s need. One example here could be offering promotions or additional inputs based on users past usage history and an appropriate user interface to highlight it. A template based engine could exactly do that by generating source during the runtime. The inputs to a template engine is a data model that feeds the input data and a template that provides where to use this data and on the fly an engine uses these inputs and provides an output. Apache Velocity is a java based template engine that can generate source during runtime. Use the following resources to get started with Apache Velocity.

• Template-Based Code Generation with Apache Velocity, Part 1
• Template-Based Code Generation with Apache Velocity, Part 2
• Velocity Users Guide

When executing a project keeping track of the issues from the quality control team as well as keeping track of issues from customers/users is the key to making sure that they are prioritized and fixed. Having a manual system for such a need can be vulnerable for human errors as well as chances of missing them is high. An issue tracking system is a must for every organization. An issue tracking system should not only be available for the project team but should also be accessible for the customers/users to post the issues they find. There are many open source as well as commercial issue tracking systems available. This recent article in JavaWorld “What issue tracking system is best for you?” discusses three issue management tools, Bugzilla, JIRA and Trac. Another open source tool that is quite good is Mantis which is a PHP based open source issue management tool. Nevertheless technology doesn’t matter but selecting a right issue tracking tool that will fit your organization as well as help customers post the issues through a system is a must.

Thanks to my friend Kanmani who sent me a link that has information how to be an effective programmer. In fact TechMasala’s foundation series of posts main objective is also to list down certain technical as well as soft skills to be an effective programmer. The document covers tips and best practices under the categories of personal and team skills for a beginner, intermediate and advanced programmer. “How to be a Programmer: A Short, Comprehensive, and Personal Summary” is a good read for every programmer.

When an expression or a block of code is passed as a parameter to a function or method then the piece of code that gets passed is called a closure in programming language terms. Closure is not something new and has been supported in programming languages like Smalltalk, Lisp, Python etc. A closure is like nameless functions within functions. Closures are supported in Ruby and are called blocks. A simple closure example in Ruby would be,

5.times {puts “Hello World”}

This prints “Hello World” five times. This code is the equivalent of the below code,

for i in 1..5
puts “Hello World”
end

Complex closures can be tricky to understand but once a developer gets the point how it works it could simplify or complex depending on the problem in hand and where it is applied. Some programming languages like Java don’t support closures yet. Is closures really handy or inconvenience? Read this article “Crossing borders: Closures” for more insights.

When it comes to the production environment it is a real test for the application as the users start using the application. It is very important that the performance of the application is something that has to be proactively measured and is a continuous constant effort to get the production environment fine tuned to the need. As far as Rails is concerned there are few insights here and there on the scalability and performance of the application. Stefan Kaes has written a package called Railsbench consisting of some Ruby and shell script code that can do some performance measurement of Rails application. Complementing the plugin is this article by Stefan on “A Look at Common Performance Problems in Rails” that talks about some common performance problems. But as mentioned by Stefan in the article some analysis of the performance of the application is necessary to apply the relevant changes to the application.

I had posted a reference article “Vista - To go or not to” where I had mentioned that if everything what you need to work on is available on a desktop operating system that comes for free then why pay so much for an operating system such as Vista. Well if you say that Windows has cool visual effects that can be unmatched, hold on, watch this YouTube video “Don’t Buy Windows Vista - Get Ubuntu for free“. Though the windows manager for linux add-on Beryl project is in its earlier stages, it is there. More good things on the visual effects to come on the Linux desktop systems. A significant advantage is that they work on a regular PC that doesn’t require hi-fi system configuration.

Happy Weekend!

Also see - “Linux Desktop Based Development Environment“.

JUnit is a great tool for unit testing Java applications but it is little difficult to apply it and test the flow from a web application perspective. Particularly say you have unit tests for your DAO you will have to use the JDBC driver connection class to connect to the database and cannot test through JNDI as it requires a server environment. Try JUnitEE. From the site,

JUnitEE provides a TestRunner which outputs HTML and a servlet which can be used as an entry point to your test cases. Building your test harness as a standard J2EE web application means:

• Your tests are packaged conveniently into a .war file which can easily be moved between servers; you can leave the .war file in the main .ear file and simply avoid enabling the test web application on the production server.
• Your test classes will be dynamically reloaded by the app server (assuming your server supports this).
• Your test cases look just like your production code, and can use the same beans (or whatever) you use as a facade for your EJBs.