In this tutorial, we will go through the logger providing feature. It’s not the most complex framework’s part but it’s a useful annotation and time saver, though. It’s allowed to use @Log with any logging tool. To do that you need to define a NamedLoggerProvider:
import org.brooth.jeta.log.NamedLoggerProvider;
public class MyLoggerProvider implements NamedLoggerProvider<MyLogger> {
private static MyLoggerProvider instance = new MyLoggerProvider();
public static MyLoggerProvider getInstance() {
return instance;
}
public MyLogger get(String name) {
MyLogger logger = new MyLogger();
logger.setName(name);
return logger;
}
}
The second step - you should pass it to LogController, but let’s create a helper method in our MetaHelper:
public static void createLogger(Object master) {
new LogController(metasitory, master).createLoggers(MyLoggerProvider.getInstance());
}
If you aren’t familiar with MetaHelper, you’d better go through this guide first.
Now, you can supply loggers into your classes. Note By default the name of the logger equals master’s name, but if you need to, you can define any other using value argument - @Log("MyName").
Hello, World!
Let’s output Hello, World! message from HelloWorld sample.
public class HelloWorldSample {
@Log
MyLogger logger;
@SayHello
String str;
public HelloWorldSample() {
MetaHelper.createLoggers(this);
MetaHelper.setHelloWorld(this);
logger.info(str);
}
}
The result is going to be like:
> Info[HelloWorldSample]: Hello, World!
