The main difference between Gilead and Hibernate4GWT is that more proxy information is stored on POJO.
A simple test would be to switch to stateful mode. If it works well, it could mean that there is too much proxy information sent to FF :-/
Regards
Bruno
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does anyone had this error on firefox (windows):
(InternalError): script too large
fileName: http://localhost:8080/nc.kroc.fmp.AppMain/58FEAEBA24ED94C41276805F8F8...
lineNumber: 444
stack: vub()@:0
eval(
I post it here as the only difference with my previous versions which was working, is a
library replacement: h4gwt 1.1 -> gilead 1.2
But I guest it's not a gilead problem so i also post it on google group :
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/c6630c08287ddb0c#
But if anyone has an idea... I'm puzzled :)
Vincent
Hi Vincent,
The main difference between Gilead and Hibernate4GWT is that more proxy information is stored on POJO.
A simple test would be to switch to stateful mode. If it works well, it could mean that there is too much proxy information sent to FF :-/
Regards
Bruno
I workaround this problem:
In fact my rpc call was too large (around 1Mo). So I simply reduce the size of theses calls to 10Ko.
I didn't take time to test in stateful mode, sorry.
Vincent