Over a million developers have joined DZone.

More (Powerful) Code Templates in NetBeans IDE 6.9

DZone's Guide to

More (Powerful) Code Templates in NetBeans IDE 6.9

· Java Zone ·
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!

In NetBeans there are some useful Code Templates, like “sout” which, when you type it in the editor and hit “Tab” will be expanded to “System.out.println();”. But you’re not limited to the predefined ones, you can also create your own templates. I’ve been playing around with Code Templates recently and was a bit disappointed, because the available set of default parameters is quite limited. E.g., I tried to add some nice templates for logging, and I was missing a way to get hold of the class name of the current file. As a workaround I did something like:

java.util.logging.Logger.getLogger(getClass()”getName()).log(java.util.logging.Level.INFO}, “${cursor}”);

I asked on the maling list if there is no other way, and I received an answer by Michel Graciano that there are a couple of Templates related to Logging that add the class name. I replied that I had looked at every single Template and none of them is related to Logging, when he said he uses 6.9 M1. And there it is, shortcut “log”:

${loggerType type=”java.util.logging.Logger” default=”Logger” editable=”false”}.getLogger(${classVar editable=”false” currClassName
type=”java.util.logging.Level” editable=”false”
default=”Level”}.${logLevel default=”INFO” completionInvoke},

“currClassname” adds the functionality I’ve been missing. (Actually I think default=”getClass()” doesn’t make much sense, because it would be expanded to “…getClass().class.getName()..” (?)).

There’s also “loge” for logging errors and “logp” for logging with parameters… Thanks Michel!

Reposted from http://eppleton.sharedhost.de/blog.

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}