Is this 'concrete type' als valid for a DTO object in GWT-RPC?
For example, I have a TestDTO object, which needs to be transferred via
GWT-RPC.
*public class TestDTO implements IsSerializable { public
ArrayList data; public List operation() {
return null;
*A new experimental version of Elemental2 using the new JsInterop
specification has been pushed on Sonatype today.*
I just tested websocket functionality of Elemental2, it works very fine for
me.
I am curious if there is any functionality difference between Elemental1
and 2?
When can I
I have the same issue and just verified how it happens.
I compare the tomcat log file with the tomcat access log file
66.249.88.115 - - [15/Jan/2016:09:09:20 +0100] "POST /datalint/service/user
HTTP/1.1" 500 57
66.249.88.95 - - [15/Jan/2016:09:09:21 +0100] "POST /datalint/service/user
The easiest solution is using tomcat8, see
https://tomcat.apache.org/tomcat-8.0-doc/default-servlet.html#change
*If a gzipped version of a file exists (a file with .gz appended to the
file name located alongside the original file), Tomcat will serve the
gzipped file if the user agent supports
