Re: working in beta but not in latest git

On Tue, Aug 9, 2016 at 3:15 PM, Jens <jens.nehlmeier@gmail.com> wrote:

Which alternate syntax? You can either call those methods or don't call them.

https://github.com/gwtproject/gwt/issues/9356 suggests that
   value.@Boolean::booleanValue() is rejected but value@Boolean::booleanValue()() works?

https://github.com/gwtproject/gwt/issues/9242

has more info on the matter at least for me because I am not grasping the root of the problem here. Something about devirtualized methods but I don't know how it maps from java to js to JSNi...

So you would need to wrap your "call the method and lets see if it might fail because its not a Java Boolean" code with try-catch. 

This is what I did. I am trying and waiting to see if/when/how it breaks. However it's not my code so I can't the tell from the usage pattern.

 

I think you can just remove the method check when using GWT 2.8.

I think that's very interesting. #9242 suggests that java Boolean is not a custom object anymore and is mapped directly to JS boolean. That means the third clause of the if statement may be indeed redundant as you say.

--

Vassilis Virvilis

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.