Re: Is there an easy way to use GWT Request Factory?

[hprc]

cool!
Simple things are good.
The main purpose is to be easy and quick to do, rather than complicate.
2022年5月25日水曜日 8:11:39 UTC+9 Craig Mitchell:

> I'm using GWT-RPC, and it works great!
>
> I have a version number (that is used by the client and server) that I 
> update when I make a breaking RPC change.  If the client detects it has a 
> different version number to the server, it shows the user a message that 
> they need to refresh their browser, as a new version has been released.
>
> Probably not the optimum solution, but it works fine for my needs.
>
> On Wednesday, 25 May 2022 at 8:15:50 am UTC+10 hprc wrote:
>
>> thank you for the advice
>> I have a poor understanding of Maven, so I can only add functionality in 
>> the basic way.
>>
>> I know myself
>> 1 Build and run using Eclipse and GWT plugin
>> 2 Add jar to build path
>> 3 Add by adding  tag
>>
>> If you prefer, it would be helpful if you could download the jars you 
>> need for domino-rest.
>>
>> 2022年5月24日火曜日 22:16:47 UTC+9 frank.h...@googlemail.com:
>>
>>>
>>> You can use domino-rest without using maven. But Maven will make things 
>>> much easier.
>>>
>>> There are several examples demontrating the use of the Domino-Stack 
>>> (including domino-rest) Also, in most cases, it does not depend on Eclipse. 
>>> F.e.: check: 
>>> https://github.com/NaluKit/nalu-examples/tree/main/nalu-complex-app-example.
>>>  
>>> This example demonstrate how to do things in Nalu. This example uses 
>>> domino-rest for the communication. (I am pretty sure Ahmad & Rafat have 
>>> similar examples using the domino stack). Just follow the instructions 
>>> inside the readme.txt. All you need to do is to install Java and Maven and 
>>> make it available from your terminal. 
>>>
>>>
>>> hprc schrieb am Dienstag, 24. Mai 2022 um 02:15:12 UTC+2:
>>>
 Re [domino-rest]
 It's a great API, you can use POJO and REST respectively.
 However, I don't know how to use ECLIPSE + GWT + MOVEN, so it's sad 
 that I can't use it right away.

>>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/b72262fd-70b3-4d04-842c-32cad5c6305dn%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[Craig Mitchell]

I'm using GWT-RPC, and it works great!

I have a version number (that is used by the client and server) that I 
update when I make a breaking RPC change.  If the client detects it has a 
different version number to the server, it shows the user a message that 
they need to refresh their browser, as a new version has been released.

Probably not the optimum solution, but it works fine for my needs.

On Wednesday, 25 May 2022 at 8:15:50 am UTC+10 hprc wrote:

> thank you for the advice
> I have a poor understanding of Maven, so I can only add functionality in 
> the basic way.
>
> I know myself
> 1 Build and run using Eclipse and GWT plugin
> 2 Add jar to build path
> 3 Add by adding  tag
>
> If you prefer, it would be helpful if you could download the jars you need 
> for domino-rest.
>
> 2022年5月24日火曜日 22:16:47 UTC+9 frank.h...@googlemail.com:
>
>>
>> You can use domino-rest without using maven. But Maven will make things 
>> much easier.
>>
>> There are several examples demontrating the use of the Domino-Stack 
>> (including domino-rest) Also, in most cases, it does not depend on Eclipse. 
>> F.e.: check: 
>> https://github.com/NaluKit/nalu-examples/tree/main/nalu-complex-app-example. 
>> This example demonstrate how to do things in Nalu. This example uses 
>> domino-rest for the communication. (I am pretty sure Ahmad & Rafat have 
>> similar examples using the domino stack). Just follow the instructions 
>> inside the readme.txt. All you need to do is to install Java and Maven and 
>> make it available from your terminal. 
>>
>>
>> hprc schrieb am Dienstag, 24. Mai 2022 um 02:15:12 UTC+2:
>>
>>> Re [domino-rest]
>>> It's a great API, you can use POJO and REST respectively.
>>> However, I don't know how to use ECLIPSE + GWT + MOVEN, so it's sad that 
>>> I can't use it right away.
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/782f571c-7389-4eff-9804-95dbd1c419fen%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[hprc]

thank you for the advice
I have a poor understanding of Maven, so I can only add functionality in 
the basic way.

I know myself
1 Build and run using Eclipse and GWT plugin
2 Add jar to build path
3 Add by adding  tag

If you prefer, it would be helpful if you could download the jars you need 
for domino-rest.

2022年5月24日火曜日 22:16:47 UTC+9 frank.h...@googlemail.com:

>
> You can use domino-rest without using maven. But Maven will make things 
> much easier.
>
> There are several examples demontrating the use of the Domino-Stack 
> (including domino-rest) Also, in most cases, it does not depend on Eclipse. 
> F.e.: check: 
> https://github.com/NaluKit/nalu-examples/tree/main/nalu-complex-app-example. 
> This example demonstrate how to do things in Nalu. This example uses 
> domino-rest for the communication. (I am pretty sure Ahmad & Rafat have 
> similar examples using the domino stack). Just follow the instructions 
> inside the readme.txt. All you need to do is to install Java and Maven and 
> make it available from your terminal. 
>
>
> hprc schrieb am Dienstag, 24. Mai 2022 um 02:15:12 UTC+2:
>
>> Re [domino-rest]
>> It's a great API, you can use POJO and REST respectively.
>> However, I don't know how to use ECLIPSE + GWT + MOVEN, so it's sad that 
>> I can't use it right away.
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/24848137-6977-4856-8abf-f0275494a6c0n%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

['Frank Hossfeld' via GWT Users]

You can use domino-rest without using maven. But Maven will make things 
much easier.

There are several examples demontrating the use of the Domino-Stack 
(including domino-rest) Also, in most cases, it does not depend on Eclipse. 
F.e.: 
check: 
https://github.com/NaluKit/nalu-examples/tree/main/nalu-complex-app-example. 
This example demonstrate how to do things in Nalu. This example uses 
domino-rest for the communication. (I am pretty sure Ahmad & Rafat have 
similar examples using the domino stack). Just follow the instructions 
inside the readme.txt. All you need to do is to install Java and Maven and 
make it available from your terminal. 


hprc schrieb am Dienstag, 24. Mai 2022 um 02:15:12 UTC+2:

> Re [domino-rest]
> It's a great API, you can use POJO and REST respectively.
> However, I don't know how to use ECLIPSE + GWT + MOVEN, so it's sad that I 
> can't use it right away.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/af91eff0-b471-4c17-96bb-e73fc7a4c07bn%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[hprc]

If you share "POJO", you can use the refactoring function of Eclipse to 
improve the maintenance performance of the entire system.

2022年5月24日火曜日 15:26:42 UTC+9 ralph.f...@gmail.com:

> I consider this as the biggest advantage: you keep type-safety across 
> client/server calls. If you do some breaking changes, the compiler will 
> tell you! I definitely prefer this above finding out at runtime…
> You can always achieve higher levels of flexibility by adding abstraction 
> layers between between hour client and server code - without loosing strict 
> type checking. 
>
> Rogelio Flores  schrieb am Mo. 23. Mai 2022 um 
> 19:37:
>
>> The big disadvantage that I see with gwt-rpc is that it ties your 
>> client-side with your server-side code (if you change anything related to 
>> your models/rpc on the client side, you also have to update your serve-side 
>> code, otherwise, it will not work). To me that in itself is a big 
>> disadvantage. With something like REST APIs, your client and server side 
>> code remain decoupled, giving you more freedom.
>>
>> On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:
>>
>>> why not use gwt-rpc? I am a lazy guy and am happily using it for more 
>>> than 10 years now - I even use the generated serializers in combination 
>>> with WebSockets. What can possibly go wrong here...?
>>>
>>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>>
 Short answer: don't start using RequestFactory now, it's been 
 practically unmaintained for years.

 Long answer: there's not really a longer answer actually, it's OK to 
 keep using RF in existing projects (if you can't afford moving to 
 something 
 else), but don't start anything with it now.
 (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)

 On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:

> I know that GWT Request Factor plays an important role in Java object 
> persistence and communication between client and server.
> However, on the server and client, even one object needs to generate 
> related classes and interfaces, and then annotation settings etc. need to 
> be set for each class and interface.
> It is complicated and has a lot of trouble to create.
>
> Originally, these things are like plugins, and it is desirable to 
> select one object and generate a related class, but do you all know?
>
> I have been using GWT for over 10 years, but I do not use 
> "RequestFactory" and operate only with objects like Map by RPC 
> communication.
> This can simplify the entire system and greatly reduce the effort 
> required to create it.
>
> GWT RequestFactory
> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>
 -- 
 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-tool...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
  
 
 .

>>> -- 
>> 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-tool...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/e3334aae-7ad4-49d9-8644-c2b6cfe9f065n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/d60afcc4-552a-4f85-9b25-89d315e4fd29n%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[Ralph Fiergolla]

I consider this as the biggest advantage: you keep type-safety across
client/server calls. If you do some breaking changes, the compiler will
tell you! I definitely prefer this above finding out at runtime…
You can always achieve higher levels of flexibility by adding abstraction
layers between between hour client and server code - without loosing strict
type checking.

Rogelio Flores  schrieb am Mo. 23. Mai 2022 um
19:37:

> The big disadvantage that I see with gwt-rpc is that it ties your
> client-side with your server-side code (if you change anything related to
> your models/rpc on the client side, you also have to update your serve-side
> code, otherwise, it will not work). To me that in itself is a big
> disadvantage. With something like REST APIs, your client and server side
> code remain decoupled, giving you more freedom.
>
> On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:
>
>> why not use gwt-rpc? I am a lazy guy and am happily using it for more
>> than 10 years now - I even use the generated serializers in combination
>> with WebSockets. What can possibly go wrong here...?
>>
>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>
>>> Short answer: don't start using RequestFactory now, it's been
>>> practically unmaintained for years.
>>>
>>> Long answer: there's not really a longer answer actually, it's OK to
>>> keep using RF in existing projects (if you can't afford moving to something
>>> else), but don't start anything with it now.
>>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>>>
>>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>>>
 I know that GWT Request Factor plays an important role in Java object
 persistence and communication between client and server.
 However, on the server and client, even one object needs to generate
 related classes and interfaces, and then annotation settings etc. need to
 be set for each class and interface.
 It is complicated and has a lot of trouble to create.

 Originally, these things are like plugins, and it is desirable to
 select one object and generate a related class, but do you all know?

 I have been using GWT for over 10 years, but I do not use
 "RequestFactory" and operate only with objects like Map by RPC
 communication.
 This can simplify the entire system and greatly reduce the effort
 required to create it.

 GWT RequestFactory
 https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html

>>> --
>>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/e3334aae-7ad4-49d9-8644-c2b6cfe9f065n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACwwWxO9yB8OapamsQDx9yCtxu0T3Mwnaa0KRuXP0uf__rjdVw%40mail.gmail.com.

Re: Is there an easy way to use GWT Request Factory?

[hprc]

Re [domino-rest]
It's a great API, you can use POJO and REST respectively.
However, I don't know how to use ECLIPSE + GWT + MOVEN, so it's sad that I 
can't use it right away.

2022年5月24日火曜日 8:07:33 UTC+9 m.conr...@gmail.com:

> Take a look at domino-rest: https://github.com/DominoKit/domino-rest
>
> You can use a shared POJOs project between the client and server projects 
> with common POJOs annotated with Jackson JSON annotations to transfer data 
> as JSON objects between client and server in a bidirectional fashion.
>
> On Mon, May 23, 2022 at 6:33 PM hprc  wrote:
>
>> I think it's a great design method.
>> Client side and server
>> Side communication should be loosely coupled.
>>
>> However, although I understand this merit, maintenance is possible more 
>> intuitively because the Java object set in the shared package is used for 
>> communication between the two.
>> Normally, when using the RESET API etc., conversion work such as parsing 
>> is required.
>>
>> 2022年5月24日火曜日 2:37:05 UTC+9 Rogelio Flores:
>>
>>> The big disadvantage that I see with gwt-rpc is that it ties your 
>>> client-side with your server-side code (if you change anything related to 
>>> your models/rpc on the client side, you also have to update your serve-side 
>>> code, otherwise, it will not work). To me that in itself is a big 
>>> disadvantage. With something like REST APIs, your client and server side 
>>> code remain decoupled, giving you more freedom.
>>>
>>> On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:
>>>
 why not use gwt-rpc? I am a lazy guy and am happily using it for more 
 than 10 years now - I even use the generated serializers in combination 
 with WebSockets. What can possibly go wrong here...?

 On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  
 wrote:

> Short answer: don't start using RequestFactory now, it's been 
> practically unmaintained for years.
>
> Long answer: there's not really a longer answer actually, it's OK to 
> keep using RF in existing projects (if you can't afford moving to 
> something 
> else), but don't start anything with it now.
> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>
> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>
>> I know that GWT Request Factor plays an important role in Java object 
>> persistence and communication between client and server.
>> However, on the server and client, even one object needs to generate 
>> related classes and interfaces, and then annotation settings etc. need 
>> to 
>> be set for each class and interface.
>> It is complicated and has a lot of trouble to create.
>>
>> Originally, these things are like plugins, and it is desirable to 
>> select one object and generate a related class, but do you all know?
>>
>> I have been using GWT for over 10 years, but I do not use 
>> "RequestFactory" and operate only with objects like Map by RPC 
>> communication.
>> This can simplify the entire system and greatly reduce the effort 
>> required to create it.
>>
>> GWT RequestFactory
>> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>>
> -- 
> 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-tool...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
>  
> 
> .
>
 -- 
>> 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-tool...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/f52fd06a-b57b-4a47-bc53-f376a6e179e8n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/acb4bd1c-b447-4895-9112-0791b9302921n%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[Michael Conrad]

Take a look at domino-rest: https://github.com/DominoKit/domino-rest

You can use a shared POJOs project between the client and server projects
with common POJOs annotated with Jackson JSON annotations to transfer data
as JSON objects between client and server in a bidirectional fashion.

On Mon, May 23, 2022 at 6:33 PM hprc  wrote:

> I think it's a great design method.
> Client side and server
> Side communication should be loosely coupled.
>
> However, although I understand this merit, maintenance is possible more
> intuitively because the Java object set in the shared package is used for
> communication between the two.
> Normally, when using the RESET API etc., conversion work such as parsing
> is required.
>
> 2022年5月24日火曜日 2:37:05 UTC+9 Rogelio Flores:
>
>> The big disadvantage that I see with gwt-rpc is that it ties your
>> client-side with your server-side code (if you change anything related to
>> your models/rpc on the client side, you also have to update your serve-side
>> code, otherwise, it will not work). To me that in itself is a big
>> disadvantage. With something like REST APIs, your client and server side
>> code remain decoupled, giving you more freedom.
>>
>> On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:
>>
>>> why not use gwt-rpc? I am a lazy guy and am happily using it for more
>>> than 10 years now - I even use the generated serializers in combination
>>> with WebSockets. What can possibly go wrong here...?
>>>
>>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>>
 Short answer: don't start using RequestFactory now, it's been
 practically unmaintained for years.

 Long answer: there's not really a longer answer actually, it's OK to
 keep using RF in existing projects (if you can't afford moving to something
 else), but don't start anything with it now.
 (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)

 On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:

> I know that GWT Request Factor plays an important role in Java object
> persistence and communication between client and server.
> However, on the server and client, even one object needs to generate
> related classes and interfaces, and then annotation settings etc. need to
> be set for each class and interface.
> It is complicated and has a lot of trouble to create.
>
> Originally, these things are like plugins, and it is desirable to
> select one object and generate a related class, but do you all know?
>
> I have been using GWT for over 10 years, but I do not use
> "RequestFactory" and operate only with objects like Map by RPC
> communication.
> This can simplify the entire system and greatly reduce the effort
> required to create it.
>
> GWT RequestFactory
> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>
 --
 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-tool...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
 
 .

>>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/f52fd06a-b57b-4a47-bc53-f376a6e179e8n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CAFHWztyJ%2BizrXLgB040Wxj%3DJ3tO0Z91xKmpLnmrLfwswhx%2Bq_A%40mail.gmail.com.

Re: Is there an easy way to use GWT Request Factory?

[hprc]

I think it's a great design method.
Client side and server
Side communication should be loosely coupled.

However, although I understand this merit, maintenance is possible more 
intuitively because the Java object set in the shared package is used for 
communication between the two.
Normally, when using the RESET API etc., conversion work such as parsing is 
required.

2022年5月24日火曜日 2:37:05 UTC+9 Rogelio Flores:

> The big disadvantage that I see with gwt-rpc is that it ties your 
> client-side with your server-side code (if you change anything related to 
> your models/rpc on the client side, you also have to update your serve-side 
> code, otherwise, it will not work). To me that in itself is a big 
> disadvantage. With something like REST APIs, your client and server side 
> code remain decoupled, giving you more freedom.
>
> On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:
>
>> why not use gwt-rpc? I am a lazy guy and am happily using it for more 
>> than 10 years now - I even use the generated serializers in combination 
>> with WebSockets. What can possibly go wrong here...?
>>
>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>
>>> Short answer: don't start using RequestFactory now, it's been 
>>> practically unmaintained for years.
>>>
>>> Long answer: there's not really a longer answer actually, it's OK to 
>>> keep using RF in existing projects (if you can't afford moving to something 
>>> else), but don't start anything with it now.
>>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>>>
>>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>>>
 I know that GWT Request Factor plays an important role in Java object 
 persistence and communication between client and server.
 However, on the server and client, even one object needs to generate 
 related classes and interfaces, and then annotation settings etc. need to 
 be set for each class and interface.
 It is complicated and has a lot of trouble to create.

 Originally, these things are like plugins, and it is desirable to 
 select one object and generate a related class, but do you all know?

 I have been using GWT for over 10 years, but I do not use 
 "RequestFactory" and operate only with objects like Map by RPC 
 communication.
 This can simplify the entire system and greatly reduce the effort 
 required to create it.

 GWT RequestFactory
 https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html

>>> -- 
>>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f52fd06a-b57b-4a47-bc53-f376a6e179e8n%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[Rogelio Flores]

The big disadvantage that I see with gwt-rpc is that it ties your 
client-side with your server-side code (if you change anything related to 
your models/rpc on the client side, you also have to update your serve-side 
code, otherwise, it will not work). To me that in itself is a big 
disadvantage. With something like REST APIs, your client and server side 
code remain decoupled, giving you more freedom.

On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:

> why not use gwt-rpc? I am a lazy guy and am happily using it for more than 
> 10 years now - I even use the generated serializers in combination with 
> WebSockets. What can possibly go wrong here...?
>
> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>
>> Short answer: don't start using RequestFactory now, it's been practically 
>> unmaintained for years.
>>
>> Long answer: there's not really a longer answer actually, it's OK to keep 
>> using RF in existing projects (if you can't afford moving to something 
>> else), but don't start anything with it now.
>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>>
>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>>
>>> I know that GWT Request Factor plays an important role in Java object 
>>> persistence and communication between client and server.
>>> However, on the server and client, even one object needs to generate 
>>> related classes and interfaces, and then annotation settings etc. need to 
>>> be set for each class and interface.
>>> It is complicated and has a lot of trouble to create.
>>>
>>> Originally, these things are like plugins, and it is desirable to select 
>>> one object and generate a related class, but do you all know?
>>>
>>> I have been using GWT for over 10 years, but I do not use 
>>> "RequestFactory" and operate only with objects like Map by RPC 
>>> communication.
>>> This can simplify the entire system and greatly reduce the effort 
>>> required to create it.
>>>
>>> GWT RequestFactory
>>> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>>>
>> -- 
>> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/e3334aae-7ad4-49d9-8644-c2b6cfe9f065n%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[hprc]

It's wise not to use Request Factory, right?
However, since it is also described in the official document, I think that 
there are people who are interested.
I have to fix these documents as well.
For example, deprecated ...

2022年5月21日土曜日 21:07:22 UTC+9 t.br...@gmail.com:

> Using ORMs on clients and servers, what are you talking about?
>
> On Saturday, May 21, 2022 at 3:27:25 AM UTC+2 hprc wrote:
>
>> to: t.br ..
>> thank you for the advice.
>> Right now I'm not using [RequestFactory] right now, so I'm not having any 
>> issues, but it's interesting to be able to use ORMs on clients and servers, 
>> isn't it?
>>
>> I myself create a data sharing type object in there and exchange it.
>>
>> 2022年5月20日金曜日 23:14:58 UTC+9 ralph.f...@gmail.com:
>>
>>> why not use gwt-rpc? I am a lazy guy and am happily using it for more 
>>> than 10 years now - I even use the generated serializers in combination 
>>> with WebSockets. What can possibly go wrong here...?
>>>
>>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>>
 Short answer: don't start using RequestFactory now, it's been 
 practically unmaintained for years.

 Long answer: there's not really a longer answer actually, it's OK to 
 keep using RF in existing projects (if you can't afford moving to 
 something 
 else), but don't start anything with it now.
 (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)

 On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:

> I know that GWT Request Factor plays an important role in Java object 
> persistence and communication between client and server.
> However, on the server and client, even one object needs to generate 
> related classes and interfaces, and then annotation settings etc. need to 
> be set for each class and interface.
> It is complicated and has a lot of trouble to create.
>
> Originally, these things are like plugins, and it is desirable to 
> select one object and generate a related class, but do you all know?
>
> I have been using GWT for over 10 years, but I do not use 
> "RequestFactory" and operate only with objects like Map by RPC 
> communication.
> This can simplify the entire system and greatly reduce the effort 
> required to create it.
>
> GWT RequestFactory
> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>
 -- 
 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-tool...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
  
 
 .

>>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/91c9fd09-749c-4e3f-9ccd-d3d9226f282dn%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[Thomas Broyer]

Using ORMs on clients and servers, what are you talking about?

On Saturday, May 21, 2022 at 3:27:25 AM UTC+2 hprc wrote:

> to: t.br ..
> thank you for the advice.
> Right now I'm not using [RequestFactory] right now, so I'm not having any 
> issues, but it's interesting to be able to use ORMs on clients and servers, 
> isn't it?
>
> I myself create a data sharing type object in there and exchange it.
>
> 2022年5月20日金曜日 23:14:58 UTC+9 ralph.f...@gmail.com:
>
>> why not use gwt-rpc? I am a lazy guy and am happily using it for more 
>> than 10 years now - I even use the generated serializers in combination 
>> with WebSockets. What can possibly go wrong here...?
>>
>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>
>>> Short answer: don't start using RequestFactory now, it's been 
>>> practically unmaintained for years.
>>>
>>> Long answer: there's not really a longer answer actually, it's OK to 
>>> keep using RF in existing projects (if you can't afford moving to something 
>>> else), but don't start anything with it now.
>>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>>>
>>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>>>
 I know that GWT Request Factor plays an important role in Java object 
 persistence and communication between client and server.
 However, on the server and client, even one object needs to generate 
 related classes and interfaces, and then annotation settings etc. need to 
 be set for each class and interface.
 It is complicated and has a lot of trouble to create.

 Originally, these things are like plugins, and it is desirable to 
 select one object and generate a related class, but do you all know?

 I have been using GWT for over 10 years, but I do not use 
 "RequestFactory" and operate only with objects like Map by RPC 
 communication.
 This can simplify the entire system and greatly reduce the effort 
 required to create it.

 GWT RequestFactory
 https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html

>>> -- 
>>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/1b992fd0-3692-4d0b-a9ca-0a7a41f9e329n%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[hprc]

to: ralph.f

thank you for the advice.
I'm using gwt-rpc now and I'm pretty happy with it.
2022年5月21日土曜日 10:27:25 UTC+9 hprc:

> to: t.br ..
> thank you for the advice.
> Right now I'm not using [RequestFactory] right now, so I'm not having any 
> issues, but it's interesting to be able to use ORMs on clients and servers, 
> isn't it?
>
> I myself create a data sharing type object in there and exchange it.
>
> 2022年5月20日金曜日 23:14:58 UTC+9 ralph.f...@gmail.com:
>
>> why not use gwt-rpc? I am a lazy guy and am happily using it for more 
>> than 10 years now - I even use the generated serializers in combination 
>> with WebSockets. What can possibly go wrong here...?
>>
>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>
>>> Short answer: don't start using RequestFactory now, it's been 
>>> practically unmaintained for years.
>>>
>>> Long answer: there's not really a longer answer actually, it's OK to 
>>> keep using RF in existing projects (if you can't afford moving to something 
>>> else), but don't start anything with it now.
>>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>>>
>>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>>>
 I know that GWT Request Factor plays an important role in Java object 
 persistence and communication between client and server.
 However, on the server and client, even one object needs to generate 
 related classes and interfaces, and then annotation settings etc. need to 
 be set for each class and interface.
 It is complicated and has a lot of trouble to create.

 Originally, these things are like plugins, and it is desirable to 
 select one object and generate a related class, but do you all know?

 I have been using GWT for over 10 years, but I do not use 
 "RequestFactory" and operate only with objects like Map by RPC 
 communication.
 This can simplify the entire system and greatly reduce the effort 
 required to create it.

 GWT RequestFactory
 https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html

>>> -- 
>>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/861de327-9666-4ed4-87fa-b406a9e0f12an%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[hprc]

to: t.br ..
thank you for the advice.
Right now I'm not using [RequestFactory] right now, so I'm not having any 
issues, but it's interesting to be able to use ORMs on clients and servers, 
isn't it?

I myself create a data sharing type object in there and exchange it.

2022年5月20日金曜日 23:14:58 UTC+9 ralph.f...@gmail.com:

> why not use gwt-rpc? I am a lazy guy and am happily using it for more than 
> 10 years now - I even use the generated serializers in combination with 
> WebSockets. What can possibly go wrong here...?
>
> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>
>> Short answer: don't start using RequestFactory now, it's been practically 
>> unmaintained for years.
>>
>> Long answer: there's not really a longer answer actually, it's OK to keep 
>> using RF in existing projects (if you can't afford moving to something 
>> else), but don't start anything with it now.
>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>>
>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>>
>>> I know that GWT Request Factor plays an important role in Java object 
>>> persistence and communication between client and server.
>>> However, on the server and client, even one object needs to generate 
>>> related classes and interfaces, and then annotation settings etc. need to 
>>> be set for each class and interface.
>>> It is complicated and has a lot of trouble to create.
>>>
>>> Originally, these things are like plugins, and it is desirable to select 
>>> one object and generate a related class, but do you all know?
>>>
>>> I have been using GWT for over 10 years, but I do not use 
>>> "RequestFactory" and operate only with objects like Map by RPC 
>>> communication.
>>> This can simplify the entire system and greatly reduce the effort 
>>> required to create it.
>>>
>>> GWT RequestFactory
>>> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>>>
>> -- 
>> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/bbdef318-f9b7-471d-8645-0eb44d6cf20fn%40googlegroups.com.

Re: Is there an easy way to use GWT Request Factory?

[Ralph Fiergolla]

why not use gwt-rpc? I am a lazy guy and am happily using it for more than
10 years now - I even use the generated serializers in combination with
WebSockets. What can possibly go wrong here...?

On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:

> Short answer: don't start using RequestFactory now, it's been practically
> unmaintained for years.
>
> Long answer: there's not really a longer answer actually, it's OK to keep
> using RF in existing projects (if you can't afford moving to something
> else), but don't start anything with it now.
> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)
>
> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:
>
>> I know that GWT Request Factor plays an important role in Java object
>> persistence and communication between client and server.
>> However, on the server and client, even one object needs to generate
>> related classes and interfaces, and then annotation settings etc. need to
>> be set for each class and interface.
>> It is complicated and has a lot of trouble to create.
>>
>> Originally, these things are like plugins, and it is desirable to select
>> one object and generate a related class, but do you all know?
>>
>> I have been using GWT for over 10 years, but I do not use
>> "RequestFactory" and operate only with objects like Map by RPC
>> communication.
>> This can simplify the entire system and greatly reduce the effort
>> required to create it.
>>
>> GWT RequestFactory
>> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACwwWxMAOGGV6xGpvq7nzW%3D29cOMGE0%2B6KA7B1UVRhgqa4_%3DyQ%40mail.gmail.com.

Re: Is there an easy way to use GWT Request Factory?

[Thomas Broyer]

Short answer: don't start using RequestFactory now, it's been practically 
unmaintained for years.

Long answer: there's not really a longer answer actually, it's OK to keep 
using RF in existing projects (if you can't afford moving to something 
else), but don't start anything with it now.
(I wouldn't start anything new with gwt-rpc either BTW, but YMMV)

On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:

> I know that GWT Request Factor plays an important role in Java object 
> persistence and communication between client and server.
> However, on the server and client, even one object needs to generate 
> related classes and interfaces, and then annotation settings etc. need to 
> be set for each class and interface.
> It is complicated and has a lot of trouble to create.
>
> Originally, these things are like plugins, and it is desirable to select 
> one object and generate a related class, but do you all know?
>
> I have been using GWT for over 10 years, but I do not use "RequestFactory" 
> and operate only with objects like Map by RPC communication.
> This can simplify the entire system and greatly reduce the effort required 
> to create it.
>
> GWT RequestFactory
> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com.

Is there an easy way to use GWT Request Factory?

[hprc]

I know that GWT Request Factor plays an important role in Java object 
persistence and communication between client and server.
However, on the server and client, even one object needs to generate 
related classes and interfaces, and then annotation settings etc. need to 
be set for each class and interface.
It is complicated and has a lot of trouble to create.

Originally, these things are like plugins, and it is desirable to select 
one object and generate a related class, but do you all know?

I have been using GWT for over 10 years, but I do not use "RequestFactory" 
and operate only with objects like Map by RPC communication.
This can simplify the entire system and greatly reduce the effort required 
to create it.

GWT RequestFactory
https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/abfd7592-548d-4be9-ac25-427b697e1cc9n%40googlegroups.com.

Re: GWT request factory - Fire request inside of success method of another request

[salk31]

Assuming you removed the extra GWT.create (as Thomas mentioned on 
stackoverflow).. if might be worth trying putting the second call inside a 
Scheduler.get().scheduleFinally...

Seems odd. I'm sure we do this sort of thing (less directly) all the time.

On Wednesday, July 17, 2013 8:21:30 PM UTC+1, Jan wrote:
>
> You mean renaming the inner request method? I tried that -> doesn't change 
> anything.
>
> It is not only in prod mode. It's a GWT test case that I run locally.
>
> Am Montag, 15. Juli 2013 23:29:14 UTC+2 schrieb Thomas Broyer:
>>
>> It's always worth mentionning when you also posted to StackOverflow: 
>> http://stackoverflow.com/q/17577892/116472
>>
>> Just an idea: did you try renaming your variables so you don't have 
>> shadowing? (if it happens only in prod mode, there could be a bug in the 
>> GWT compiler)
>>
>> On Monday, July 15, 2013 10:10:48 PM UTC+2, Jan wrote:
>>>
>>> I am trying to nest two request factory calls in each other. I retrieve 
>>> a post object and in the success-method i use the same object again (just 
>>> for testing purposes, I get the same behavior for other request like for 
>>> example persisting).
>>>
>>> The problem is: Only the first request reaches the server.
>>>
>>> I don't get any error message. If I debug the code, everything works 
>>> until the second request is fired. Nothing happens then. The method on the 
>>> backend is not called, the frontend shows no error, even if I implement the 
>>> "onFailure"-method for the receiver of the second request.
>>>
>>> public class RequestFactoryFindTest extends GWTTestCase{
>>>
>>> /**
>>>  * must refer to a valid module that sources this class.
>>>  */
>>> public String getModuleName() {
>>> return "com.Test.MyTest";
>>> }
>>>
>>> public void test(){
>>> final ClientFactory clientFactory = 
>>> GWT.create(ClientFactoryImpl.class);
>>> final MyRequestFactory requestFactory = 
>>> clientFactory.getRequestFactory();
>>> final PostRequest request = requestFactory.postRequest();
>>>
>>>
>>> request.findPost(1l).fire(new Receiver() {
>>>
>>> @Override
>>> public void onSuccess(PostProxy response) {
>>>
>>>
>>> final ClientFactory clientFactory = 
>>> GWT.create(ClientFactoryImpl.class);
>>> final MyRequestFactory requestFactory = 
>>> clientFactory.getRequestFactory();
>>> final PostRequest request = requestFactory.postRequest();
>>>
>>> System.out.println("outer success");
>>>
>>> request.findPost(1l).fire(new Receiver() {
>>>
>>> @Override
>>> public void onSuccess(PostProxy response) {
>>> System.out.println("inner success");
>>>
>>> }
>>>
>>> });
>>>
>>> }
>>> });
>>>
>>>
>>> }}
>>>
>>> Can someone explain this?
>>>
>>>

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

Re: GWT request factory - Fire request inside of success method of another request

[Jan]

You mean renaming the inner request method? I tried that -> doesn't change 
anything.

It is not only in prod mode. It's a GWT test case that I run locally.

Am Montag, 15. Juli 2013 23:29:14 UTC+2 schrieb Thomas Broyer:
>
> It's always worth mentionning when you also posted to StackOverflow: 
> http://stackoverflow.com/q/17577892/116472
>
> Just an idea: did you try renaming your variables so you don't have 
> shadowing? (if it happens only in prod mode, there could be a bug in the 
> GWT compiler)
>
> On Monday, July 15, 2013 10:10:48 PM UTC+2, Jan wrote:
>>
>> I am trying to nest two request factory calls in each other. I retrieve a 
>> post object and in the success-method i use the same object again (just for 
>> testing purposes, I get the same behavior for other request like for 
>> example persisting).
>>
>> The problem is: Only the first request reaches the server.
>>
>> I don't get any error message. If I debug the code, everything works 
>> until the second request is fired. Nothing happens then. The method on the 
>> backend is not called, the frontend shows no error, even if I implement the 
>> "onFailure"-method for the receiver of the second request.
>>
>> public class RequestFactoryFindTest extends GWTTestCase{
>>
>> /**
>>  * must refer to a valid module that sources this class.
>>  */
>> public String getModuleName() {
>> return "com.Test.MyTest";
>> }
>>
>> public void test(){
>> final ClientFactory clientFactory = 
>> GWT.create(ClientFactoryImpl.class);
>> final MyRequestFactory requestFactory = 
>> clientFactory.getRequestFactory();
>> final PostRequest request = requestFactory.postRequest();
>>
>>
>> request.findPost(1l).fire(new Receiver() {
>>
>> @Override
>> public void onSuccess(PostProxy response) {
>>
>>
>> final ClientFactory clientFactory = 
>> GWT.create(ClientFactoryImpl.class);
>> final MyRequestFactory requestFactory = 
>> clientFactory.getRequestFactory();
>> final PostRequest request = requestFactory.postRequest();
>>
>> System.out.println("outer success");
>>
>> request.findPost(1l).fire(new Receiver() {
>>
>> @Override
>> public void onSuccess(PostProxy response) {
>> System.out.println("inner success");
>>
>> }
>>
>> });
>>
>> }
>> });
>>
>>
>> }}
>>
>> Can someone explain this?
>>
>>

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

Re: GWT request factory - Fire request inside of success method of another request

[Thomas Broyer]

It's always worth mentionning when you also posted to 
StackOverflow: http://stackoverflow.com/q/17577892/116472

Just an idea: did you try renaming your variables so you don't have 
shadowing? (if it happens only in prod mode, there could be a bug in the 
GWT compiler)

On Monday, July 15, 2013 10:10:48 PM UTC+2, Jan wrote:
>
> I am trying to nest two request factory calls in each other. I retrieve a 
> post object and in the success-method i use the same object again (just for 
> testing purposes, I get the same behavior for other request like for 
> example persisting).
>
> The problem is: Only the first request reaches the server.
>
> I don't get any error message. If I debug the code, everything works until 
> the second request is fired. Nothing happens then. The method on the 
> backend is not called, the frontend shows no error, even if I implement the 
> "onFailure"-method for the receiver of the second request.
>
> public class RequestFactoryFindTest extends GWTTestCase{
>
> /**
>  * must refer to a valid module that sources this class.
>  */
> public String getModuleName() {
> return "com.Test.MyTest";
> }
>
> public void test(){
> final ClientFactory clientFactory = 
> GWT.create(ClientFactoryImpl.class);
> final MyRequestFactory requestFactory = 
> clientFactory.getRequestFactory();
> final PostRequest request = requestFactory.postRequest();
>
>
> request.findPost(1l).fire(new Receiver() {
>
> @Override
> public void onSuccess(PostProxy response) {
>
>
> final ClientFactory clientFactory = 
> GWT.create(ClientFactoryImpl.class);
> final MyRequestFactory requestFactory = 
> clientFactory.getRequestFactory();
> final PostRequest request = requestFactory.postRequest();
>
> System.out.println("outer success");
>
> request.findPost(1l).fire(new Receiver() {
>
> @Override
> public void onSuccess(PostProxy response) {
> System.out.println("inner success");
>
> }
>
> });
>
> }
> });
>
>
> }}
>
> Can someone explain this?
>
>

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

GWT request factory - Fire request inside of success method of another request

[Jan]

I am trying to nest two request factory calls in each other. I retrieve a 
post object and in the success-method i use the same object again (just for 
testing purposes, I get the same behavior for other request like for 
example persisting).

The problem is: Only the first request reaches the server.

I don't get any error message. If I debug the code, everything works until 
the second request is fired. Nothing happens then. The method on the 
backend is not called, the frontend shows no error, even if I implement the 
"onFailure"-method for the receiver of the second request.

public class RequestFactoryFindTest extends GWTTestCase{

/**
 * must refer to a valid module that sources this class.
 */
public String getModuleName() {
return "com.Test.MyTest";
}

public void test(){
final ClientFactory clientFactory = GWT.create(ClientFactoryImpl.class);
final MyRequestFactory requestFactory = 
clientFactory.getRequestFactory();
final PostRequest request = requestFactory.postRequest();


request.findPost(1l).fire(new Receiver() {

@Override
public void onSuccess(PostProxy response) {


final ClientFactory clientFactory = 
GWT.create(ClientFactoryImpl.class);
final MyRequestFactory requestFactory = 
clientFactory.getRequestFactory();
final PostRequest request = requestFactory.postRequest();

System.out.println("outer success");

request.findPost(1l).fire(new Receiver() {

@Override
public void onSuccess(PostProxy response) {
System.out.println("inner success");

}

});

}
});


}}

Can someone explain this?

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

Re: Gwt Request factory

[deepak chauhan]

@Stefan: I am using Spring for injecting the implementation.

@Thomas: This is the answer I was looking for. Multiple requestContext is
good solution.

Thanks for your precious support.


On Mon, Apr 15, 2013 at 6:46 PM, Thomas Broyer  wrote:

>
>
> On Monday, April 15, 2013 10:38:49 AM UTC+2, deepak chauhan wrote:
>>
>> Hi All,
>>
>> I am using gwt request factory. But, there is one design issue I am
>> facing. As per the proxy design in RequestContext interface I can only
>> declare one service in @service annotation. But there are situations where
>> many methods in the context can be served by different services. But, due
>> to design constraint, I have to put the all context methods in same service.
>>
>
> Why is it so? Why can't you create several RequestContext? If it's about
> batching, there's RequestContext#append().
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Deepak Chauhan

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

Re: Gwt Request factory

[Thomas Broyer]

On Monday, April 15, 2013 10:38:49 AM UTC+2, deepak chauhan wrote:
>
> Hi All,
>
> I am using gwt request factory. But, there is one design issue I am 
> facing. As per the proxy design in RequestContext interface I can only 
> declare one service in @service annotation. But there are situations where 
> many methods in the context can be served by different services. But, due 
> to design constraint, I have to put the all context methods in same service.
>

Why is it so? Why can't you create several RequestContext? If it's about 
batching, there's RequestContext#append(). 

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

Re: Gwt Request factory

[Stefan Ollinger]

Can you create a service implementation which forwards to the concrete 
services?

Alternatively you can create a proxy for each service.

On 15.04.2013 10:38, deepak chauhan wrote:

Hi All,

I am using gwt request factory. But, there is one design issue I am 
facing. As per the proxy design in RequestContext interface I can only 
declare one service in @service annotation. But there are situations 
where many methods in the context can be served by different services. 
But, due to design constraint, I have to put the all context methods 
in same service.


Can somebody tell me the better way to get it done


--
Deepak Chauhan
--
You received this message because you are subscribed to the Google 
Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to google-web-toolkit+unsubscr...@googlegroups.com.

To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.




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

Gwt Request factory

[deepak chauhan]

Hi All,

I am using gwt request factory. But, there is one design issue I am facing.
As per the proxy design in RequestContext interface I can only declare one
service in @service annotation. But there are situations where many methods
in the context can be served by different services. But, due to design
constraint, I have to put the all context methods in same service.

Can somebody tell me the better way to get it done


-- 
Deepak Chauhan

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

Re: Spring and gwt (request factory)

[Miłosz Pacholczyk]

Hello, 

have you found a way to configure it properly? 

If so, would you mind posting samples for web.xml and 
applicationContext.xml?
I have a very similiar code, but I got stuck at wiring it all.

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

Re: Spring and gwt (request factory)

[pierre leagault]

i have something similar but more generic.

public class SpringServiceLocator implements ServiceLocator {

@Override
public Object getInstance(Class clazz) {
HttpServletRequest request = 
RequestFactoryServlet.getThreadLocalRequest();
ServletContext servletContext = 
request.getSession().getServletContext();
ApplicationContext context = 
WebApplicationContextUtils.getWebApplicationContext(servletContext);
return context.getBean(clazz);
}
}

@ProxyFor(value=Account.class, locator = AccountLocator.class)
public interface AccountProxy extends EntityProxy{

}

public class AccountLocator extends Locator {

@Autowired
private AccountDAO accountDAO;

@Override
public Account create(Class clazz) {
return new Account();

}

@Override
public Account find(Class clazz, Long id) {
...
}
...
}

@Service(locator = SpringServiceLocator.class, value =AccountService.class)
public interface AccountRequest extends RequestContext {
 ...
}

Le jeudi 23 août 2012 23:02:38 UTC+2, pierre leagault a écrit :
>
> hi
>
> i use spring and gwt (request factory).
>
> in my applicationContext, i use context component-scan but my bean is not 
> retrieved.
>
> i need to declare it manually.
>
> why component scan don't work?
>
>
> my web.xml
>
> 
> contextConfigLocation
> /WEB-INF/applicationContext.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
>
> 
> requestFactoryServlet
> 
> com.google.web.bindery.requestfactory.server.RequestFactoryServlet
> 
>
> 
> requestFactoryServlet
> /gwtRequest
> 
>
> 
> 
> welcomeGWT.html
> 
>
>
> thanks
>
>

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

Re: Spring and gwt (request factory)

[Alfredo Quiroga-Villamil]

This might not directly answer your question but it'll hopefully help.
You will find all the moving pieces you need there. In my DAO, I am
injecting via @Autowired some beans (not shown in the example).

Proxy:
===
@ProxyFor(value = Card.class, locator = CardLocator.class)
public interface CardProxy extends EntityProxy {
.
===

Entity:
===
@Table(name = "cards")
@Entity
public class Card {

public class CardLocator extends Locator{

@Override
public Card create(Class clazz) {
return new Card();
}

@Override
public Card find(Class clazz, Integer id) {
return ((CardDAO) BeanContextUtil.getBean(CardDAO.class)).find(id);
}
.
===

RequestContext:
===
@Service(value = CardDAO.class, locator = CardServiceLocator.class)
public interface CardRequestContext extends RequestContext {

===

DAO:
===
@Component
public class CardDAO {

===

Service Locator:
===
public class CardServiceLocator implements ServiceLocator {

@Override
public Object getInstance(Class clazz) {
return BeanContextUtil.getBean(CardDAO.class);
}

}
===

Bean Util:
===
public class BeanContextUtil {

public BeanContextUtil() {

}

public static Object getBean(Class clazz) {
HttpServletRequest request =
RequestFactoryServlet.getThreadLocalRequest();
ServletContext servletCtx = request.getSession().getServletContext();
ApplicationContext springCtx =
WebApplicationContextUtils.getWebApplicationContext(servletCtx);
return springCtx.getBean(clazz);
}

}
===

Best regards,

Alfredo

On Sat, Aug 25, 2012 at 10:35 AM, pierre leagault
 wrote:
> my service class is annoted with service and my dao with repository
>
> Le jeudi 23 août 2012 23:02:38 UTC+2, pierre leagault a écrit :
>>
>> hi
>>
>> i use spring and gwt (request factory).
>>
>> in my applicationContext, i use context component-scan but my bean is not
>> retrieved.
>>
>> i need to declare it manually.
>>
>> why component scan don't work?
>>
>>
>> my web.xml
>>
>> 
>> contextConfigLocation
>> /WEB-INF/applicationContext.xml
>> 
>>
>> 
>>
>> org.springframework.web.context.ContextLoaderListener
>> 
>>
>> 
>> requestFactoryServlet
>>
>> com.google.web.bindery.requestfactory.server.RequestFactoryServlet
>> 
>>
>> 
>> requestFactoryServlet
>> /gwtRequest
>> 
>>
>>
>> 
>> welcomeGWT.html
>> 
>>
>>
>> thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/xLI56yX5k3MJ.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.



-- 
Alfredo Quiroga-Villamil

AOL/Yahoo/Gmail/MSN IM:  lawwton

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Spring and gwt (request factory)

[pierre leagault]

my service class is annoted with service and my dao with repository

Le jeudi 23 août 2012 23:02:38 UTC+2, pierre leagault a écrit :
>
> hi
>
> i use spring and gwt (request factory).
>
> in my applicationContext, i use context component-scan but my bean is not 
> retrieved.
>
> i need to declare it manually.
>
> why component scan don't work?
>
>
> my web.xml
>
> 
> contextConfigLocation
> /WEB-INF/applicationContext.xml
> 
> 
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
>
> 
> requestFactoryServlet
> 
> com.google.web.bindery.requestfactory.server.RequestFactoryServlet
> 
>
> 
> requestFactoryServlet
> /gwtRequest
> 
>
> 
> 
> welcomeGWT.html
> 
>
>
> thanks
>
>

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

Re: Spring and gwt (request factory)

[Alfredo Quiroga-Villamil]

In addition to declaring the base package where Spring will start to
search for your "Beans", you have to also annotate the class with
@Component.

Best regards,

Alfredo

On Thu, Aug 23, 2012 at 5:02 PM, pierre leagault
 wrote:
> hi
>
> i use spring and gwt (request factory).
>
> in my applicationContext, i use context component-scan but my bean is not 
> retrieved.
>
> i need to declare it manually.
>
> why component scan don't work?
>
>
> my web.xml
>
> 
> contextConfigLocation
> /WEB-INF/applicationContext.xml
> 
>
> 
> 
> org.springframework.web.context.ContextLoaderListener
> 
>
> 
> requestFactoryServlet
> 
> com.google.web.bindery.requestfactory.server.RequestFactoryServlet
> 
>
> 
> requestFactoryServlet
> /gwtRequest
> 
>
>
> 
> welcomeGWT.html
> 
>
>
> thanks
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google Web Toolkit" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/google-web-toolkit/-/4QrWjBivh5YJ.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-web-toolkit?hl=en.
>



-- 
Alfredo Quiroga-Villamil

AOL/Yahoo/Gmail/MSN IM:  lawwton

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Spring and gwt (request factory)

[pierre leagault]

hi

i use spring and gwt (request factory).

in my applicationContext, i use context component-scan but my bean is not 
retrieved.

i need to declare it manually.

why component scan don't work?


my web.xml


contextConfigLocation
/WEB-INF/applicationContext.xml




org.springframework.web.context.ContextLoaderListener

   

requestFactoryServlet

com.google.web.bindery.requestfactory.server.RequestFactoryServlet



requestFactoryServlet
/gwtRequest




welcomeGWT.html



thanks

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

Re: Tutorial for GWT request factory and Android

[Thomas Broyer]

You'll use RequestFactorySource.create() instead of GWT.create(), and pass 
a UrlRequestTransport or a RequestTransport of your own (possibly using 
Apache HttpClient) to the initialize() method.

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

Tutorial for GWT request factory and Android

[Shrivallabh]

Hi Folks,

I have an existing app built on GWT 2.4 which makes use of GWT request
factory.

I am planning to write an android app that exposes a subset of
functionality and has a different look and feel.

However, the means to fetch data remains the same - request factory.

Is there any tutorial available for hooking android apps with Request
factory?

I have read that requestfactory-client should help us do exactly that.

Any pointers will be immensely helpful.

regards,


Shrivallabh

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

GWT Request Factory JSON specification, Delphi integration

[Boris]

I really like GWT and RF. I would like to connect a client Delphi
application with Hibernate, but I haven't found a good way yet. I am
thinking of using Request Factory. So basically Delphi app has to
parse and build JSON responses, requests. I have set up a java app
with hibernate, Request factory servlet and GWT proxys. Now I have to
parse JSON responds from GWT RF in Delphi application. I would like to
know, if there is any specification on how RF JSON messages are build/
formed.

The next step would be to build JSON request for updating, saving and
deleting data.

Thanks,
Boris

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT Request Factory Entity @NotNull Validation doesnt seem to be working

[Owen Ilagan]

Thanks!

On Apr 16, 6:46 am, Thomas Broyer  wrote:
> Annotating your classes/fields/accessors is not enough; you need a tool that
> uses those annotations. gwt-servlet-deps only contains the javax.validation
> annotations, not any actual validator.
> Try adding hibernate-validator.jar in your classpath, and see if it makes a
> difference (I bet it will)

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT Request Factory Entity @NotNull Validation doesnt seem to be working

[Thomas Broyer]

Annotating your classes/fields/accessors is not enough; you need a tool that 
uses those annotations. gwt-servlet-deps only contains the javax.validation 
annotations, not any actual validator.
Try adding hibernate-validator.jar in your classpath, and see if it makes a 
difference (I bet it will)

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT Request Factory Entity @NotNull Validation doesnt seem to be working

[Owen Ilagan]

I meant, I just use plain appengine via JDO.

On Apr 15, 6:11 pm, Owen Ilagan  wrote:
> I dont use Hibernate, just JDO and the javax.validation annotation
> classes that came with
> gwt-servlet-deps.jar which I already included in my classpath. Am I
> supposed to use another
> library? I dont see any "Unable to initialize a JSR 303 Bean
> Validator" errors on my console
> either.
>
> On Apr 15, 5:36 pm, Thomas Broyer  wrote:
>
>
>
>
>
>
>
> > Just in case: I suppose you have some JSR 303 validator (hibernate
> > validator, for instance) in your classpath?
> > If you see the "Unable to initialize a JSR 303 Bean Validator" log in the
> > console, then it's not going to work, as it simply won't validate anything.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT Request Factory Entity @NotNull Validation doesnt seem to be working

[Owen Ilagan]

I dont use Hibernate, just JDO and the javax.validation annotation
classes that came with
gwt-servlet-deps.jar which I already included in my classpath. Am I
supposed to use another
library? I dont see any "Unable to initialize a JSR 303 Bean
Validator" errors on my console
either.

On Apr 15, 5:36 pm, Thomas Broyer  wrote:
> Just in case: I suppose you have some JSR 303 validator (hibernate
> validator, for instance) in your classpath?
> If you see the "Unable to initialize a JSR 303 Bean Validator" log in the
> console, then it's not going to work, as it simply won't validate anything.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT Request Factory Entity @NotNull Validation doesnt seem to be working

[Thomas Broyer]

Just in case: I suppose you have some JSR 303 validator (hibernate 
validator, for instance) in your classpath?
If you see the "Unable to initialize a JSR 303 Bean Validator" log in the 
console, then it's not going to work, as it simply won't validate anything.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

GWT Request Factory Entity @NotNull Validation doesnt seem to be working

[Owen Ilagan]

Hi!

So I finally got Request Factory to work on my Eclipse environment and
I'm trying out the Entity validation features. Following the example
on the tutorial, I add @NotNull to my Entity class property like so:

import javax.validation.constraints.NotNull;
@Entity
public class Employee {
  @NotNull
  private String userName;
 ...

Then I try to trigger the onViolation callback by using:

AppRequestFactory factory = clientfactory.getAppRequestFactory();
EmployeeRequest context = factory.employeeRequest();
EmployeeProxy employeeProxy = context.create(EmployeeProxy.class);
employeeProxy.setDepartment("New Department");
employeeProxy.setPassword("password");
employeeProxy.setUserName(null);
context.add(employeeProxy).fire(new Receiver() {
...

Unfortunately, the add method succeeds every time I run it even if the
userName property is not set or purposely set to null, as in this
case. Is there something I'm missing here? I haven't tried the other
validation options yet since I can't get something this simple to work
and they'll probably get the same result as this.

Although it might not be related, I'm also not using any Locators for
this entity and use @ProxyForName because of a bug in GWT Plugin for
Eclipse.

- Owen

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.