On Mon, Mar 18, 2019 at 6:33 PM <kevin.harri...@twomen.com> wrote: > > Elias, thank you for the prompt response and submitting a fix. > > I have checked this out, and though it does result in successful compilation, > it does not solve my problem because the public constructor is removed > allowing me no initializer access from the application side. I had attempted > to fix this issue by removing the constructor before because it is not used > internally. >
I see. I think it's possible to keep your constructors by not using constructors for the internal initialization of proxy objects. However, that's a bigger change so I kept the fix small by skipping the offending constructor. Perhaps you could use Go "int" types for your constructors instead of "int32". I believe that will generate a non-clashing constructor that takes a Java long instead of an Java int. - elias -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
