Closed GoogleCodeExporter closed 8 years ago
Hi,
I could imagine that the problem is already solved by the solution of issue 27
(http://code.google.com/p/gwteventservice/issues/detail?id=27) which was
committed today to the trunk version, because there are some optimizations with
removing listeners. It would be great if you could try it again with the trunk
version.
Thank you in advance.
Regards,
Sven S.
Original comment by sven.strohschein@googlemail.com
on 29 Jan 2011 at 4:34
This issue could now be reproduced with the description of Issue34. This
problem should not have negative effects to the application but the exception
should of course be avoided.
Original comment by sven.strohschein@googlemail.com
on 3 Oct 2011 at 10:49
Status code 0 is sent by some browsers when the browser/user navigates to
another site/application and is actually not an error, but GWT inteprets this
as a StatusCodeException. In the case of GWT applications it should be an
unimportant status code because the GWT module is unloaded in that case.
Status code 0 is now handled correctly by GWTEventService and will no longer be
logged as an error (fixed in the trunk version and in the upcoming 1.2 release
candidate).
Original comment by sven.strohschein@googlemail.com
on 3 Oct 2011 at 4:03
Hi)
Thank you very much for your work.
I'm sorry for taking so long to reply, due to lack of time i haven't tried to
run trunk version yet..sorry, i will)
Regards,
Peter.
Original comment by PeterTur...@gmail.com
on 4 Oct 2011 at 1:45
Original issue reported on code.google.com by
PeterTur...@gmail.com
on 22 Nov 2010 at 10:54Attachments: