Hi Andy Wilkinson,

Ah yes, the issue with Kotlin and enums, I debugged this one as the OP originally came to us. I'm well aware of it.

So about the javadoc not saying anything about that, I must admit that we didn't expect this case: the main issue here is that the reflection API and the parameter name provider don't return consistent results so we can't really do anything about it.

I thought about being more clever in HV but couldn't find a reliable solution as I have no idea where the missing parameters are so I can't really affect a name to the parameters (except a default $i name).

We could maybe add a check but the issue is that, right now, the resolution of parameter names is done at runtime. This is something I want to change as it would be better to resolve them at bootstrap once and for all but it has some ramifications regarding the XML/programmatic API bootstrap and we are not there yet.

If we manage to resolve them at bootstrap, then we could add a check and a nice log message. Otherwise, we will pretty much fill the logs of the user with warning messages and that wouldn't be a good thing.