Thanks Jeff for your response. It was about a "transacted" operation. The error went away after I programatically register class aliases for 2 more Message classes in my Module. So I think it was again due to the fact the message the client sent did not have the "alias" ready for the server to use ..The question still remains (I posted it on my other message threads today):
http://tech.groups.yahoo.com/group/flexcoders/message/93121 <http://tech.groups.yahoo.com/group/flexcoders/message/93121> http://tech.groups.yahoo.com/group/flexcoders/message/93208 <http://tech.groups.yahoo.com/group/flexcoders/message/93208> why do i need to programatically register all these aliases within my Module, to successfully talk to LCDS, why aren't they automatically made available - or what should I do to produce that, when compiling the module? This is what I have so far (the last 2 were just added - they solved this problem I posted here). I'm using both DataService and RemoteObject classes in my Module. The code below is added on my Module's constructor. Thanks, Robert registerClassAlias( "flex.messaging.messages.RemotingMessage", mx.messaging.messages.RemotingMessage ); registerClassAlias( "flex.data.messages.DataMessage", mx.data.messages.DataMessage ); registerClassAlias( "flex.data.messages.SequencedMessage", mx.data.messages.SequencedMessage ); registerClassAlias( "flex.data.messages.UpdateCollectionMessage", mx.data.messages.UpdateCollectionMessage ); registerClassAlias( "flex.data.UpdateCollectionRange", mx.data.UpdateCollectionRange ); --- In [email protected], "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > That is very strange. Can you reproduce that with the server debug > logging enabled on the server for the "Message.*" and "Endpoint.*" > patterns enabled (in WEB-INF/flex/services-config.xml, set level="Debug" > and make sure those patterns are in the tags below). > > > > Unfortunately the error does not include the message which is causing > the error. It should be either a "batched" or "transacted" type of > message. The "body" of those types of messages is supposed to be an > array of DataMessages but somehow we are getting an untyped "ASObject" > in there. > > > > Jeff > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Robert Csiki > Sent: Friday, November 09, 2007 10:21 AM > To: [email protected] > Subject: [flexcoders] Unhandled failure on the server (LC Data Services) > > > > Got this error when the DataService updates a collection with LCDS. Any > ideas? I'm using LCDS 2.5.1 and FlexBuilder 2.0.1 with hotfix 2 Thanks. > > errorReply: Flex Message (flex.messaging.messages.ErrorMessage) > clientId = 11D8F786-5719-0DA9-EF74-78B603160B85 > correlationId = 1AF666B8-F92C-FC3D-8117-25A0268AF09C > destination = repositoryObjectAssembler > messageId = 11DC0268-DF1C-5543-9C64-76A36441D3C5 > timestamp = 1194632161359 > timeToLive = 0 > body = null > code = Server.Processing > message = There was an unhandled failure on the server. > flex.messaging.io.amf.ASObject > details = null > rootCause = null > body = null > extendedData = null > stackTrace for: java.lang.ClassCastException: > flex.messaging.io.amf.ASObject > flex! > .data.DataService.serviceTransactedMessage(DataService.java:744) > flex.data.DataService.serviceMessage(DataService.java:429) > > flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:11 > 65) > > flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoin > t.java:757) > > flex.messaging.endpoints.rtmp.AbstractRTMPServer.dispatchMessage(Abstrac > tRTMPServer.java:888) > > flex.messaging.endpoints.rtmp.NIORTMPConnection$RTMPReader.run(NIORTMPCo > nnection.java:424) > > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker > .runTask(ThreadPoolExecutor.java:665) > edu.emory.mathcs.backport.java.util.concurrent.Thr! > eadPoolExecutor$Worker.run(ThreadPoolExecutor.j! ava:690) > java.lang.Thread.run(Unknown Source) >
