Can someone give me a code example? Or update the templates directly...
Jody
On Wed, Mar 24, 2010 at 1:28 AM, Justin Deoliveira wrote:
> I argued this point recently but was convinced by others that the guard
> can be necessary depending on the environment. Probably a good idea to
> guard by defa
I argued this point recently but was convinced by others that the guard
can be necessary depending on the environment. Probably a good idea to
guard by default unless one is sure it is an area that won't impact
performance.
-Justin
On 3/22/10 9:05 PM, Jody Garnett wrote:
> I usually only use t
I usually only use that if I am putting some work into the error
message; in this case I am just passing the existing message along.
On Tue, Mar 23, 2010 at 10:34 AM, Simone Giannecchini
wrote:
> I would use guarded logging in front a finer logging statement.
>
> Simone.
> ---
I would use guarded logging in front a finer logging statement.
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob:
Here is an example of the result:
package org.geotools.data.ows;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.geotools.util.logging.Logging;
public class Foo {
private static final Logger LOGGER = Logging.getLogger(Foo.class);
static void example(){
I went to update the code template to have this years date; and tried my hand
at including the boiler plate logger code. I even learned something; Andrea
pointed out that using the class to construct your logger survives refactoring
in ways a package string never would
codetemplates.xml
Descri
