Re: AutoBean sample not working for me?

To clarify, you need to add something like makeAddress to DoSomething: Address makeAddress() { // Construct the AutoBean AutoBean address = factory.address(); // Return the Address interface shim return address.as(); } Then you can change your code to: DoSomething test

Re: AutoBean sample not working for me?

Either that or add a method to the AutoBeanFactory taking a Person as argument to be wrapped as an AutoBean. (From memory) -- 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

Re: [gwt-contrib] Re: Elemental2 - What's the big secret?

Because Double, Boolean can now be used to get raw primitive numbers and booleans as object references, the basic JS collections will work out of the box. The Elemental1 collections had one additional benefit in the sense that there were pure-JRE implementations of interfaces. I don't think

Re: AutoBean sample not working for me?

You need to create the person by calling makePerson. Sent from my iPhone > On Jun 17, 2016, at 3:35 PM, sdfdsf dsfsdfds > wrote: > > Hi, > > I copy / pasted the AutoBean serialization example from here: > >

Re: [gwt-contrib] Re: Elemental2 - What's the big secret?

Elemental2 is purely generated; doesn't have handrolled collection/json APIs. It uses closure extern files so you can investigate what will be available checking here: https://github.com/google/closure-compiler/tree/master/externs On Fri, Jun 17, 2016 at 8:18 AM, Thomas Broyer

AutoBean sample not working for me?

Hi, I copy / pasted the AutoBean serialization example from here: http://www.gwtproject.org/doc/latest/DevGuideAutoBeans.html I've implemented the necessary interfaces etc to setup a quick test which can be summarized as follows: PersonImpl person = new PersonImpl();

Re: [gwt-contrib] Re: Elemental2 - What's the big secret?

The question I have is more general. What will the scope of Elemental 2 be? Will it include collections and json support like elemental or will it be just an interface to browser API's? On Thursday, June 16, 2016 at 4:28:08 PM UTC-4, Ray Cromwell wrote: > > > With these kinds of purely code

Re: AtomicReference

Oh, I had no idea Guava provides anything related to GWT. I would personally prefer to wait a bit longer and have this out-of-the-box in GWT, rasther than be dependant on another library. But I do understand GWT maintainers/gurus may have different opinion. Regards JZ Dne pátek 17. června

Re: AtomicReference

Oh, I had no idea Guava provides anything related to GWT. I would personally prefer to wait a bit longer and have this out-of-the-box in GWT, then depending on Guava. But I do understand GWT maintainers/gurus may have different opinion. Regards JZ Dne pátek 17. června 2016 12:59:47 UTC+2

Re: AtomicReference

That was just a suggestion. Guava is involved in the way that it already provides gwt emulation for java.util.concurrent.* classes, e.g. it has emulation of AtomicBoolean, AtomicInteger and AtomicLong. It will be easier to merge your PR to Guava because they have more frequent release cycles

Re: AtomicReference

I don't use Guava in this very project. I am completely clueless about what you are suggesting. What I wish to add to GWT is AtomicReference class (as simple as possible) and one or two *.gwt.xml files. How would Guava be involved in that? Dne pátek 17. června 2016 11:43:27 UTC+2 Andrei

construct image from Serverside to client side in GWT

Hello all, my requirement is an image getting from server to GWT client. from the client side, I send a message through AsyncCallBack method and the server response Serializable byte[] object. when getting this object, I am parsing as String object. but the image could get. the steps i

Re: AtomicReference

If you use Guava in your project, I'd send this PR to Guava since they have much frequent releases than GWT does and they accept PRs quite fast. They currently have atomic references for primitive values but not AtomicReference. On Friday, June 17, 2016 at 12:32:49 PM UTC+3, Jens wrote: > > I

Re: AtomicReference

Dne pátek 17. června 2016 11:32:49 UTC+2 Jens napsal(a): > > I can't speak for an official maintainer but I would be fine with it to > increase code compatibility. Also the emulation code is pretty straight > forward. Its likely that GWT will contain a bit more java.util.concurrent.* >

Re: AtomicReference

I can't speak for an official maintainer but I would be fine with it to increase code compatibility. Also the emulation code is pretty straight forward. Its likely that GWT will contain a bit more java.util.concurrent.* emulation in the future as long as it makes sense (e.g. CompletableFuture +

AtomicReference

Hello I am using GWT with Lombok and one of Lombok's neat features makes it believe it needs AtomicReference. In GWT context this is not actually true but still the GWT compiler is complaining. To deal with this