Re: EMF with GWT and serialize problems

[Jens]

RequirementImpl must implement serializable, needs to have a default 
constructor (visibility does not matter), no final fields and there must be 
at least one serializable type found for each field that can be assigned to 
that field (which must meet the same requirements). Also if you do not 
transfer RequirementImpl directly but instead an interface that 
RequirementImpl implements, then GWT Compiler needs to see the class+source 
of RequirementImpl so it can treat RequirementImpl as a possible concrete 
type that might be transferred. 

Have you double checked these requirements? 

-- J.


Am Dienstag, 25. August 2020 17:11:53 UTC+2 schrieb Guillen Antonio:
>
> HI all,
>
> I use GWT 2.81 and EMF (Eclipse Modeling Framework) when i want send from 
> the server to the client an object of my model, I obtain this final error:
> com.google.gwt.user.client.rpc.SerializationException: Type 
> 'com.lacen.organisation.impl.RequirementImpl' was not included in the set 
> of types which can be serialized by this SerializationPolicy or its Class 
> object could not be loaded. For security purposes, this type will not be 
> serialized.: instance = 
> com.lacen.organisation.impl.RequirementImpl@2fa144e7 (name: Fkygrdphgf)
>
> I have tried to understand how to use serializationWhitelist but I have no 
> clear example.  The class RequirementImpl contains List, so I tried to 
> create ArrayList with the good type, but same pb.
>
> Can you help me, at least give me where found a claer explanation. 
>
> Tanks a lot 
> Antonio Guillen
>

-- 
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/a9d2d1f0-8352-4b8c-a59d-60f743ddbbaao%40googlegroups.com.

Re: EMF with GWT and serialize problems

[Guillen Antonio]

HI Jens,

Thanks for your help. I don't understand this sentence " *Also if you do 
not transfer RequirementImpl directly but instead an interface that 
RequirementImpl implements, then GWT Compiler needs to see the class+source 
of RequirementImpl so it can treat RequirementImpl as a possible concrete 
type that might be transferred. " *What do you understand?
I had also read stuff on whiteList but I don't understand what means this 
WhiteList? Do you know this?

Regards
Antonio

Le mercredi 26 août 2020 à 09:29:33 UTC+2, Jens a écrit :

> RequirementImpl must implement serializable, needs to have a default 
> constructor (visibility does not matter), no final fields and there must be 
> at least one serializable type found for each field that can be assigned to 
> that field (which must meet the same requirements). Also if you do not 
> transfer RequirementImpl directly but instead an interface that 
> RequirementImpl implements, then GWT Compiler needs to see the class+source 
> of RequirementImpl so it can treat RequirementImpl as a possible concrete 
> type that might be transferred. 
>
> Have you double checked these requirements? 
>
> -- J.
>
>
> Am Dienstag, 25. August 2020 17:11:53 UTC+2 schrieb Guillen Antonio:
>>
>> HI all,
>>
>> I use GWT 2.81 and EMF (Eclipse Modeling Framework) when i want send from 
>> the server to the client an object of my model, I obtain this final error:
>> com.google.gwt.user.client.rpc.SerializationException: Type 
>> 'com.lacen.organisation.impl.RequirementImpl' was not included in the set 
>> of types which can be serialized by this SerializationPolicy or its Class 
>> object could not be loaded. For security purposes, this type will not be 
>> serialized.: instance = 
>> com.lacen.organisation.impl.RequirementImpl@2fa144e7 (name: Fkygrdphgf)
>>
>> I have tried to understand how to use serializationWhitelist but I have 
>> no clear example.  The class RequirementImpl contains List, so I tried to 
>> create ArrayList with the good type, but same pb.
>>
>> Can you help me, at least give me where found a claer explanation. 
>>
>> Tanks a lot 
>> Antonio Guillen
>>
>

-- 
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/11cc2432-8e51-4921-84c6-af035a12c17dn%40googlegroups.com.

Re: How to start with GWT upgrade from version 2.1.0 to 2.9.0, (java 1.6 to java 1.8)

[Blaze]

If its ok for you to stay with GXT2, then just use gxt 2.3.1a.jar which 
usually should work out of the box also with 2.8 and 2.9. 
For me(fairly complex project) with 2.8 and 2.9 I had some minor problems 
which I change my self directly inside the source and recompiled the jar.

Hope this helps!

p.s moving to gxt3 or gxt4 would be a lot of rewrite!!

On Tuesday, August 25, 2020 at 6:24:15 PM UTC+2 t.br...@gmail.com wrote:

>
>
> On Tuesday, August 25, 2020 at 5:49:38 PM UTC+2, Hari wrote:
>>
>> Thank you all for the quick response, from all the responses its general 
>> that it will not be complete re-write, which is a relief for sure. 
>>
>> Also I forgot to mention we were using GXT 2.2.1 and as per this doc 
>> https://docs.sencha.com/gxt/4.x/guides/getting_started/Versions.html 
>> 
>>  in 
>> order to use GWT 2.9 i will have to use GXT4.x, so i made the SDK changes 
>> and tried to build the application, with minimal changes to *.GWT.xml file, 
>> i am running into below build error.
>>
>
> Updating GXT is another matter, AFAICT this is *not* easy, as they made a 
> *lot* of breaking changes. Also, it's likely that the app will change 
> visually. Oh, and licensing.
> (I've never used GXT, so can't really help)
>
> But if your goal is only/primarily to update to Java 8, have you tried 
> whether it's possible without bumping GWT at all? or possibly not all the 
> way to 2.8/2.9? (e.g. 2.6, which is still compatible with GXT 2, as of 
> 2.3.1a)
>  
>
>>
>> [java][ERROR] Hint: Check that your module inherits 
>> 'com.google.gwt.core.Core' either directly or indirectly (most often by 
>> inheriting module 'com.google.gwt.user.User')
>>
>> Googling around on this error for some time now, but no luck. can anyone 
>> here please help me with this.
>> Also are there any other things that need to be taken care of when 
>> upgrading to gxt to 4.x? 
>>
>> Thanks
>> Hari
>>
>> On Tuesday, August 25, 2020 at 7:44:36 PM UTC+5:30 t.br...@gmail.com 
>> wrote:
>>
>>>
>>>
>>> On Tuesday, August 25, 2020 at 1:01:47 PM UTC+2, Hari wrote:

 Hi Team,

 (Apologies if the answers to my question are based on individuals 
 opinion based, but i am in dire need of your help)

 I am currently stuck with an old GWT 2.1.0 application written in Java 
 1.6 which needs to be updated to java 1.8, so we are planning to upgrade 
 to 
 latest GWT version 2.9.0. There are no changes to the application code or 
 any new enhancement request in last 5 years, considering this our client 
 is 
 expecting no changes to look and feel of the application but from the 
 compliance perspective we are required to upgrade to at least Java 1.8.

 But i have no experience and never used GWT, and there are very few 
 guides out there on upgrade from 2.1.0 to 2.9.0 (I know its a big jump). 
 Can someone help me understand, how to start the upgrade process, and how 
 much code changes would i need to make the application compatible with the 
 new version, will it be complete re-wright of the UI component of the 
 application? or will it be minor changes to existing code ? Finally, if 
 the 
 upgrade requires complete re writing of UI component, is it worth it for 
 me 
 to lean GWT (considering recent slow down in upgrades to GWT) and uses it 
 in the upgrade instead of complete rewrite of UI in React.

>>>
>>> It depends on your dependencies.
>>> GWT 2.2 had a breaking change for some third-party libraries (using GWT 
>>> generators, by turning some abstract classes into interfaces), so make sure 
>>> you also update your third-party libraries.
>>> Otherwise, things should work without too much breakage AFAICT, and 
>>> should *also* look the same (again, depending on the additional 
>>> libraries the project uses).
>>> See http://www.gwtproject.org/release-notes.html (and yes, the breaking 
>>> change in 2.2 is not documented there ¯\_(ツ)_/¯ )
>>>
>>

-- 
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/736c071e-31f6-46bb-a7d7-bd71f0443f0dn%40googlegroups.com.