Best Practice : Use of Report in Java/j2ee

Use of reporting tool like jasper, crystal, brit etc. is common in web application developed in java/j2ee or any other language. Now a days all reporting tool provide greater flexibility and comes out with lot many features. Performing certain business, displaying computed columns etc which is also possible through java. What I meant by that is for a given feature we may have two ways to perform either in Java or in Report. Now should we choose Java or Reporting tool to implement the same?
We should be little careful and should analyse which is the best way......
From my personal experience, I would go with Java to perform business rule or performing some computation instead of report.
In most reporting tool we have to first create the design file which will be translated to intermediate form like xml. Then this intermediate form will eventually converted to appropriate report form. Now if we choose reporting design file to perform computation or other business rule then sometime it would be difficult to make changes if any business rule got changed because it has to under above discussed translation. Also to modify the design file you require certain tool. For example if an application is running in production and require immediate modification then we can make the changes in Java and then redeploy into the server. It is also easy to maintain.

Regards
Monu