If there was a serialization error, it would be written out using your servlet container's own logging system - but your own service call could have had an error too and be written via your `LogManager.getLogger(getClass()).error(e); `. Can you confirm with your debugger that the call is being made correctly, and serializing properly? It might also make sense to deliberately throw an exception (both within and outside of your try/catch) and see where that log ends up.
Note that final fields are supported in gwt-rpc, but you need to set rpc.XserializeFinalFields to true in your .gwt.xml file:
<set-property name="rpc.XserializeFinalFields" value="true" />
On Wednesday, December 18, 2024 at 10:20:43 AM UTC-6 ne...@propfinancing.com wrote:
> What is the exception logged on the server that caused the HTTP 500 error?
That is the problem. I am not seeing any error on the server.
> should not have final fields
I did not realize this limitation. I am pretty sure there are some.
Looking at the docs, I will add transient to them.
Thank you,
Neil
--
Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com
We offer 30 year loans on single family houses!
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 view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/aae029ed-ac50-4c1c-933c-a744a87d8b27n%40googlegroups.com.
No comments:
Post a Comment