No. tapir relies on a couple of Scala-specific features, which won't be possible to port to Java. One example is type-safety. Every time we add a new input, with a value which maps to some request part (query, header, path, ...), the type of the value what we create is extended. This is then used to verify at compile-time that the business logic function has the correct signature - takes values of appropriate types as input as returns either the error or successful output.
I’m just wondering what do you think about using Lombok annotations in Java, do you find level of control over what happens in code with such additions enough?
When we're doing projects in Java, we use Lombok. Definitely better than generating all those getters & setters. However, it's still a hack to make Java a better language. Lombok annotations give you a good level of control, but personally when possible, I simply prefer to use a better, more powerful language (such as Scala).