Potential IAE with 4.1.1 due to deprecation fix

Question

Potential IAE with 4.1.1 due to deprecation fix

DManstrator opened this issue a year ago · comments

In commit ca30938, Constructor#isAccessible was replaced by Constructor#canAccess(null). From what I've seen within the source code, this could raise an IllegalArgumentException since null is treated as an invalid value.

I honestly don't know what else could be used but I wanted to point it out.

github-actions · Answer 1 · Wed May 24 2023 22:25:55 GMT+0800 (China Standard Time)

Thank you for contributing to Poiji! Feel free to create a PR If you want to contribute directly :)

Hakan Özler · Answer 2 · Sun Jun 04 2023 01:44:09 GMT+0800 (China Standard Time)

Hi @DManstrator , I was aware of that case. I was thinking that this unlikely happens to have IAE while debugging the code.

DMan · Answer 3 · Mon Jun 12 2023 15:05:56 GMT+0800 (China Standard Time)

I looked at the source code again and searched for example usages. The examples also use null as the param and by looking closely, the method can also throw for non-null usages. And the JavaDocs explain the following:

if this reflected object is a static member or constructor and the given {@code obj} is non-{@code null}

So I guess it is correct in this case, sorry for the inconveniences.