| Issue 540: | RPC Warning | |
| 4 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
GWT Release: 1.3 Detailed description: RPC should warn user the reason a class is not serlizable is because of missing default contructor. Workaround if you have one: Remember to create default constructors. Links to the relevant GWT Developer Forum posts: |
||||||||||||||
,
Dec 21, 2006
It would be very nice if info of why the type was not serializable showed up under the warning.
Summary: RPC Warning
|
|||||||||||||||
,
Dec 27, 2006
(No comment was entered for this change.)
Labels: -Type-Defect Type-Enhancement
|
|||||||||||||||
,
Feb 12, 2007
(No comment was entered for this change.)
Labels: Category-RPC
|
|||||||||||||||
,
Apr 12, 2007
Assigning back to Miguel, as it doesn't seem to be in my bailiwick anymore. |
|||||||||||||||
,
May 17, 2007
Fixed along with issue 933 which was committed at r1043.
Status: FixedNotReleased
|
|||||||||||||||
,
May 29, 2007
(No comment was entered for this change.)
Status: Fixed
Labels: Milestone-1_4_RC |
|||||||||||||||
|
,
May 01, 2008
Owner: ecc
|
|||||||||||||||
,
Sep 29, 2008
I'm running 1.5.2 and the issue is still there. |
|||||||||||||||
,
Dec 10, 2008
I concur that this bug is not fixed, GWT 1.5.3. If I add a no-args constructor to the class, it works fine. A better error message at least would be appreciated. |
|||||||||||||||
,
Jan 29, 2009
I can verify that this is an issue with 1.5.3. I have a class which implements an interface which extends Serializable. If that class doesn't have a default constructor I get a "myInterface was not serializable and has no concrete serializable subtypes" error. |
|||||||||||||||
 Sign in to add a comment
|
|||||||||||||||