rdifrango

Not sure why the YAML isn't showing up, but as a reference I used the YAML from this issue to make sure mine wasn't the cause: https://github.com/OpenAPITools/openapi-generator/issues/5989

ok, an update if I set the generator as `spring` then it works just fine; so this seems to be a bug in the java generator: ``` spring ```

@andrewgaul We use it sparingly as we've started to switch over to Guava, so I'll give it a shot.

I'm debating a PR to add this capability as I agree with the @markzhai that it would be good to add because I personally built something similar to this in...

@lukaseder We aren't in an OSGi environment so it's a good call that it might be detrimental there. I can tell you though in traditional environments the caching definitely is/was...

I also would like to see this feature and I wonder if there's a way to tap into the existing capabilities of logback and log4j2 as they already support syntax...

I think removing the Chainsaw component would be good given that there's a the following new CVE against it and its inclusion in the core jar: https://www.cvedetails.com/cve/CVE-2022-23307/

Thanks @ceki - I missed that.

@felixbarny the reason for needing this is covered by #144, basically being able to mask fields in environments where you are handling sensitive data would be good to have in...

@felixbarny it's not a problem per se; it just that I would like the ability to namespace them given that the spec has a placeholder for these attributes to land....