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.