Thank you both for your answers, which helped me solve the problems I
have with constraint validation.
Regarding Ralph's Log4j 1.x bridge validation:
On Sun, Feb 20, 2022 at 9:46 PM Ralph Goers wrote:
> I suspect if we simply extract the values and pass them to the Log4j 2
> component’s
> Builde
As usual you ask really good questions.
I made the builders Plugins primarily because it was an easy way to identify
them along with the class they are emulating. Other than that, the
log4j-plugins
builder type support really can’t be used as is because it operates on a Node
hierarchy while w
I added the annotations a while ago to work on reducing duplication of
constraint validation littered throughout the codebase. However, given that it
is only invoked during plugin object construction, there’s still plenty of
manual checks for things (and not much in the way of validators impleme
Hello,
Inspired by the StackOverflow question [1], where `log4j-1.2-api`
provided the user with a totally useless error message, I was looking
at the validation of components from the perspective of a Log4j 1.x
bridge `Builder` plugin. From what I found there are 3 ways to
validate parameters:
1.
