This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
DI of Custom Request/Response Objects Causes Remoting Runtime ErrorsPage Title Module
...and for some reason I simply didn't do it for all the request and response objects....probably b/c I generate them...silly me...which is why i posted it here...seemed like I was overlooking something extremely simple ;-)
In that case, I guess the post is still useful if you're doing Flash or AS3 only projects with Remoting or if you forget to put a reference to your request and response objects somewhere in the app, as the error you'll encounter isn't exactly intuitive:
TypeError: Error #1034: Type Coercion failed: cannot convert Object@13e9921 to mx.messaging.messages.ErrorMessage.
Unlike the the class not found exception with the helpful message on inclusion impls that's in the SAS framework.
NOTE: if you don't get this error you'll get it for one of the other unmapped core Remoting AS/Java objects...like:
TypeError: Error #1034: Type Coercion failed: cannot convert Object@13e9921 to flex.messaging.messages.RemotingMessage.
Thanks for pointing out my overly complex solution.
looks like I read ur post too quickly as well, the blogpost was actually yours
I thought it was just something you stumbled upon, had I known it was you I would, naturally, have been a lot more insulting and condescending.
All kidding aside, its true that the post has enough useful information on the registerClassAlias() function, which is always good.
Did you, for instance know, that when you use ObjectUtil.copy() to duplicate an object the result is untyped?
Unless, right before you make the ObjectUtil.copy() call you call the registerClassAlias().
Did you contact Christophe directly about this? Or are your SpringSource papers being processed already?
If you haven't had contact with Christophe yet, I suggest you drop him an email directly, you can get a hold of him through the developer mailinglist.
He will make sure you receive the necessary paperwork (well, PDF work).