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

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know.


Symptom: 1.The JVM became Out of memory when creating big consumption report 2.Those JRTemplateElement-instances is still there occupied even if I logged out the system
Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.The clearobjects() method in ReportThread class has not been triggered when logging out
Action I tried:      About the Virtualizer: 1.Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory     About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object                Item 4,5 – result : it helps a lot to reduce the number of  JRTemplateE…