Skip to main content

Lesson learned from current projects(ongoing)

Took a few months to be familiar with existing projects and try to fix bunch of issues reported by customer and team. Learned huge amount of things from the codes,
1. Use hibernate instead of jdbc sql. This will be extremely help to deal with the change of requirements.
2. Nice convention is necessary. The Java Class should have  the same pre-file name with the Jsp page; Should put all those similiar function codes in one place(e.g. pojo in folder Model , dao in Dao, controller in Controller ,service in folder service), put all the constants in one file(it's really helpful when you have to change them)
3. Test is important( need to plan the test before you commit the codes in production)
4. Version control. Currently, the projects running on three places. The development, staging and production.
The production running the stable codes retrieved from trunk, the staging always have the tested codes from development environment; development environment have the latest codes(some of them may be part finished - not stable).
The 100% completed codes will be moved to staging every day that the testers can test on them. The well tested   codes in staging  will be move to trunk for future deployment

5. Freemaker is good for organizing the emails to customers
6. Quartz always work correctly for the cron job
7. It will improve the speed to developing GWT by dividing the codes into multiple modules
8. to be continue...

Comments

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.


Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…