Kedar Mhaswade's Blog: December 2006 Archive

It is suggested that the preferrred way of creating the information for a Java package, such that the javadoc tool recognizes it as such, while creating the javadoc documentation.

I decided to take this advice and immediately landed into problem of inconsistency with it. I could not create this file as a Java source file, using the NetBeans IDE because it is not a proper java class name! So, I wonder why Java SE decided to take such a name. Wouldn't just packageinfo.java serve the purpose?

Am I missing something obvious?

Static Imports -- not a clean job?

Posted by km on December 23, 2006 at 05:22 PM | Permalink | Comments (22)

We have been requested to use static imports sparingly. I like that advice. Use your judgment to actually use this support.

But frankly, articles, presentations I have seen use the stdout, the "out" field of java.lang.System as imported statically. But, the following program does not compile:

class Format {
public static void main(final String[] args) {
out.format("Hello, World!");
}
}

Why?

Because I did not do: import static java.lang.System.out!

Why are all public members of the System classes not automatically
statically imported, like the System classes are imported?

Is there a problem with this expectation? Would community like implicit static import of public members of java.lang.*?

Extended Enterprise Application Platform and Java SE 6 together ...

Posted by km on December 15, 2006 at 11:02 PM | Permalink | Comments (0)

As Scott Oaks has pointed out, the Application Platform SDK (formerly known as Java EE SDK) has been released. One of the things that quickly catches the eye is on-demand attach for JConsole that Java SE 6 has. The idea is that you can now avoid the non-intuitive Java System Properties (that were essential in Java SE 5) and still manage and monitor a Java SE 6 VM, on-demand. So all you do is:

Download the platform (which has a folder name of "SDK" for some reason).

Start the default domain by doing asadmin start-domain

And when you start JConsole, you'll see the default application server domain VM right there as shown in this graphic. When you click on "Connect", it connects to the application server VM and you can monitor the entire application server VM. All the MBeans, threads, classes, memory, operating system is visible.

Powered by
Movable Type 3.01D

java.net RSS Feeds