J2EE Blogs:

J2ME Blogs:

.NET Blogs:

Important Links:

International Users:

 

M$: Another entry to hall of shame

Image is self explanatory:

posted by Kumar at 9:16 PM

 

J2SE: 10 References for 1.4.X GC

Sun has several docs for 1.4.x GC settings. Here are 10 of them:
1. Performance FAQ.
2. Java HotSpot VM Options.
3. Tuning Garbage Collection with 1.4.2.
4. Threading.
5. Big Heaps and Intimate Shared Memory.
6. Performance White Paper(1.4.2).
7. HotSpot FAQ(1.4.2).
8. Improving Java Application Performance and Scalability by Reducing Garbage Collection Times and Sizing Memory Using JDK 1.4.1.
9. Java HotSpot Virtual Machine.
10. Turbo-charging the Java HotSpot Virtual Machine, v1.4.x to Improve the Performance and Scalability of Application Servers.
posted by Kumar at 7:44 PM

 

Directories are Java source file package names

After reading this blog by Gregg Wonderly and some of the comments posted at the blog I decided to write this blog entry.
For a long time I used to think directories are not Java source file package names because Chapter 7 of Java language specification said so. Also many a times(For any product that you work on for long time) maintaining directories as Java source file package names is a pain. Imagine you are developing a product called javamagic. You are working for a oraganization which has several suborganizations and with several products for each sub organization. If your java source files must be in a directory tree mirroring the package name, your source directory would typically look something like this:

Having this structure is pain and sounds dumb because you know com/javaswamy/jone/javamagic is always constant and there is absolutely no need to maintian this filesystem hierarchy as you know what you are working on. If possible a simple hierarchy like this would be what everyone likes to have:

This is easy to navigate and presents developer view of the code.

Now lets get back to reality. Though Java Language Specification doesn't impose the restiction of Directories are Java source file package names, JavaDoc does. JavaDoc tool faq states "If your classes do not all belong to the unnamed package, you must put them in directories named after the packages.". So if you need to generate javadocs for your project and use JavaDoc tool to generate the documentation, Directories are Java source file package names.

Like many other java programmers, I would love to see JavaDoc team solve these problems that exist since JDK1.1 days:
1. Directories are Java source file package names.
2. Deprecation warning is suppressed if the compilation unit containing the deprecation is being compiled at the same time as the compilation unit using the deprecated class or member.

posted by Kumar at 10:17 AM

 

Office: OpenOffice.org 1.1 released

OpenOffice.org announced first major update to OpenOffice. 1.1 is now final and English version is available for download on Windows, Solaris and Linux. I have been using 1.0.x versions and 1.1 RC's for a while. With every update OpenOffice is getting better and better and better compatability with M$ Office. OpenOffice is now the only office suite on my home machine.
The two new major features for me in 1.1 update are export to PDF format from OpenOffice.org Writer and export to Macromedia Flash format (.swf) from OpenOffice.org Impress. Support for export to PDF got better with every update.
Checkout my blog archive for the month 2003_09 exported to PDF from Writer:Kumar Mettu's Blog.pdf. The only data lost from saved html file is Hyperlinks.
Here is a simple presentation exported to Macromedia Flash format (.swf):


Check out OpenOffice.org XML Essentials book online.
posted by Kumar at 7:25 PM