1

Since with Apache Velocity v2.0 we have moved to SLF4J, how to handle creation of velocity.log for serverless calls? For example if an AWS lambda function is calling the java code using VTL, during runtime velocity.log will not be able to create. Will an exception be thrown? Do we need to suppress velocity.log from being created? Or velocity.log creation will not happen? Earlier we were using ve.setProperty(Velocity.RUNTIME_LOG_LOGSYSTEM_CLASS,NullLogChute.class.getName()); to suppress the log file from getting created.

Current code - ve.setProperty(Velocity.RESOURCE_LOADER,"classpath"); ve.setProperty("classpath.resource.loader.class", ClasspathResourceLoader.class.getName()); ve.init();

sraipuria
  • 11
  • 2

1 Answers1

0

Switching to SLF4J implies that it's not anymore Velocity which is responsible for creating the log file. Velocity only depends on the SLF4J logging API, which expects to find a logger implementation in the classpath, see Velocity logging doc.

The easiest way to have your log file created is to add slf4j-simple to the classpath, which you can configure using system properties.

Claude Brisson
  • 4,085
  • 1
  • 22
  • 30
  • Thank you for your response! I do have @Slf4j annotation with the existing application which is used to monitor by CloudWatch. Will a new file still be created? Or will it continue to show logs only in Cloudwatch. – sraipuria Jul 10 '23 at 04:33