Remote classes returned through BlazeDS need no-argument constructorsI got caught by this one rather early in my BlazeDS journey. I created a service that return a value object type that I was mapping from the Java side to the ActionScript side. I initially had all of the property values coming in through the constructor. That won't work too well, and the errors that this produces are not very easily deduced. I'm using Cairngorm and they're value object typically have public properties, so setting the values through the constructor is probably just a silly anyways.
|
|