The reason for doing the work is to create something useful that helps people. Please click the ads if my articles are useful for you. Definitely, that's not enough. My target is working at some great organizations, such that one day, all the people with internet access can benefit from the service I contributed.
Search This Blog
A tricky of using Eclipse
When using xCode, it is always fun to tap 'ES" button and use the feature of code sense. How about Eclipse? by default, you have to type 'Ctrl+Space‘， which is a very good way to interrupt your coding feeling. As you have to move your left hand back to touch the keys.
By using ESC key, you just need to reach your little finger, Done! It's a very nice invention from apple.
To do it in Eclipse, you only need to change the hot key to 'ESC' and you then can enjoy this great feature.
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.
<band height="20" splitType="Stretch">
<textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true">
<reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/>
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