Unfortunately, the ScriptFilter won’t solve the world’s problems. I would
imagine there are plenty of environments that disallow scripting in their
production environment.
That said, I think we can do better than creating a new Filter for every thing
to be tested.
Ralph
> On Apr 5, 2024, at 1
Agree. There is no need to complicate an application just to compensate for
someone else's poor design. I am more than happy to use a script filter in
this case, I just wanted to be sure there wasn't already something there.
Robert Egan
--
*VSolvit LLC*, *CMMI (Level 3), ISO 9001, ISO 2-1, ISO
If a user can simply solve this using a `ScriptFilter`, I am not keen on
adding a custom filter to support this use case out of the box – in
particular, when the user themselves signals "a poor design" on the
application side.
I am in favor of making the custom filter implementation process as
fri
Hi Ralph,
On Thu, 4 Apr 2024 at 21:01, Ralph Goers wrote:
> I really have no idea why but this is the first time I have heard someone ask
> for the ability to filter based on the Exception class.
This came out at least once before: see the SO "Log4j - How to log
specific exception into a separa
working with an application that wraps every exception in
> a
> > general exception. The problem is, there are some errors I can address
> > (configuration errors, user errors, etc) and some I cannot address
> (network
> > errors, database errors, etc). But they are all wra
> I would like to ACCEPT only on the wrapped exceptions I can address and
> DENY the ones I cannot address. Can this be done simply through the log4j2
> configuration files, or will I need to create a custom filter?
>
> Robert Egan
>
em is, there are some errors I can address
> (configuration errors, user errors, etc) and some I cannot address (network
> errors, database errors, etc). But they are all wrapped in the general
> exception.
>
> I would like to ACCEPT only on the wrapped exceptions I can address a
exception.
I would like to ACCEPT only on the wrapped exceptions I can address and
DENY the ones I cannot address. Can this be done simply through the log4j2
configuration files, or will I need to create a custom filter?
Robert Egan
