On 7 nov, 00:46, Jack wrote:
> Oh that sounds pretty nice. Haven't realized that its possible that
> way.. hehe..and its not nasty at all :)
> I'll give it a try. Thanks!
>
> And a second question that comes to my mind:
> When using RequestFactory our domain objects are only defined by
> interfa
On 7 nov, 02:56, Jack wrote:
> Ok it works like a charm with a custom RequestTransport and a custom
> header. Thanks for that tip!
>
> But RequestFactory docs should really mention what to add to web.xml
> and that you need a json implementation from json.org and a
> javax.validation implementat
Ok it works like a charm with a custom RequestTransport and a custom
header. Thanks for that tip!
But RequestFactory docs should really mention what to add to web.xml
and that you need a json implementation from json.org and a
javax.validation implementation in your server classpath to make
things
Oh that sounds pretty nice. Haven't realized that its possible that
way.. hehe..and its not nasty at all :)
I'll give it a try. Thanks!
And a second question that comes to my mind:
When using RequestFactory our domain objects are only defined by
interfaces. Is there a class in the framework that p
On 6 nov, 19:26, Jack wrote:
> Hi,
>
> we would like to integrate GWT 2.1 RequestFactory in our application.
> Our application's backend uses JPA and has one database per customer.
> So we have to tell our EntityManagerFactory which database it should
> use, depending on the customer who did the
Hi,
we would like to integrate GWT 2.1 RequestFactory in our application.
Our application's backend uses JPA and has one database per customer.
So we have to tell our EntityManagerFactory which database it should
use, depending on the customer who did the server request.
Currently we have http://o
