Re: converting JPA entities to Records

AFAIK, you have existing interface (GWT record) ... and you want to
create a concrete implementation of that interface - if you will
choose GWT generator or APT/JSR269 processor is does not matter - both
can fullfil your needs. processor in the java compile time, generator
in the GWT compile time.

Peter

On 30. Aug, 09:57 h., Thomas Broyer <t.bro...@gmail.com> wrote:
> On 30 août, 09:25, Peter Simun <si...@seges.sk> wrote:
>
> > Thomas, why do you think that deferred binding is fail?
>
> First, you'll have to GWT.create() something to trigger your code
> generator. It would then have to be triggered before you GWT.create()
> your RequestFactory for the RequestFactoryGenerator to see the
> generated files. Last but not least, you'll have to code against your
> "generated records" (RequestFactory "requests" will probably use those
> records; and if you instead generate the RequestFactory, your calling
> code will have to deal with the records).
> Deferred binding is about generating concrete implementations for
> already defined interfaces; here you want to generate interfaces,
> which cannot be done at compile-time (like deferred binding) because
> you need to code against them.
> You might find a way to make it work, but annotation processors would
> probably also require less code and convolutions, as it's a tool made
> for this job!

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.