Santiago Acosta

I have a feeling that **LiveObjectService** is not ready for Kotlin. I used the above example from @michaelcordero and expanded it to show that it really does not matter whether...

I am really interested in this feature. If possible, and as long as it is not an encumbrance, I would like to help speed up the completion of the 3.15.1...

I have read your contribution guideline which I hadn't seen before (https://github.com/redisson/redisson/blob/redisson-3.15.0/.github/CONTRIBUTING.md ... I hadn't seen the link written below the comment box x_x) I started looking into this issue...

I recreated the test bed and provided all the dependencies to my Kotlin project. The outcome is still the same ``` Test: given private backing fields when using field accessors...

I think the issue lies more in ByteBuddy's `ElementMatchers` and the proxy interception. I am trying to write a snippet in kotlin code to see if I can emulate some...

I believe that this issue is completely contained inside the `RedissonLiveObjectService::createProxy` method and the methodology behind the configuration of the proxies. When I run the tests, the `persist` invocation persists...

I may be completely wrong but I am trying to work around both the matching and the interception inside the `createProxy` ```java private Class

I have set up on a fork what seems to be a crude initial attempt at testing kotlin classes. I don't know how to share this with you but it...

I am an idiot. The devil is in the details. I only fell off the tree when I looked into the method matchers and realized that the settings require that...

@stevenschlansker, @vahidpaz I had an issue with my enums having custom Int values (I'm working with Kotlin). I used a custom ColumnMapper for my specific enum type. Here's the link...