It does look to me like endless recursion. I already have assigned 4GB RAM for the compiler. Will try it now with 8GB and hope for the best. Since project does build successfully more often then not I am hopeful its a memory issue. Will keep you posted.
-- And will need to try with a simple custom arraylist project. The codebase is large and complex so I just created an example to share.
On Friday, March 31, 2017 at 1:54:20 PM UTC+5:30, Jens wrote:
On Friday, March 31, 2017 at 1:54:20 PM UTC+5:30, Jens wrote:
Looks like there is an recursion that is either too deep for the stack memory configured in the JVM (-xss parameter) or it's and endless recursion. Also it seems to occur while gathering serialization information, I guess for GWT-RPC. What GWT compiler does is, it looks at your GWT-RPC methods and their paramters/return types and then figures out all possible classes that could be used with these methods. So if you have serializable classes used with GWT-RPC that have an ArrayList field GWT compiler will now also analyze CustomArrayList.Does it already fail with an empty CustomArrayList implementation or did you just snip the code because you don't want to publish it?-- J.
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment