BlazeDS and Service Capture Incompatibility

December 31 2007 by Andrew Powell

When building Flex applications, I always use Service Capture to help debug remoting calls. Well, it turns out that with SC version 1.2.22, it will not read the AMF data coming from BlazeDS. It will read the data sent to BlazeDS, but not the data coming out. I am sure this will be fixed soon, but a head's up to anyone else running into this problem.

Posted in Flex | BlazeDS | ESRI | IIS | Adobe | Training | 4 comments

4 responses to “BlazeDS and Service Capture Incompatibility”

1. Rey Bango Says:
   Jan 1, 2008 at 12:00 AM <p>Andrew,</p>
   
   <p>I emailed Kevin Langdon about it. Hopefully, he'll provide some input on it.</p>
   
   <p>Have a great new year!</p>
   
   <p>Rey</p>
2. Kevin Says:
   Jan 2, 2008 at 12:00 AM <p>The problem seems to be the fact that BazeDS uses objects that extend Externalizable. As you may know these objects are simply byte arrays where the logic to serialize or deserialize them is completely within the Java or Actionscript. That means that SC really can't properly parse these without having access to the actual class definitions. I am looking into some possible solutions.</p>
3. Kevin Langdon Says:
   Jan 4, 2008 at 12:00 AM <p>The latest version (1.2.24) of ServiceCapture should resolve most issues with BlazeDS.</p>
4. Rey Bango Says:
   Jan 4, 2008 at 12:00 AM <p>Very cool Kevin. Glad you were able to tackle that. :)</p>

Leave a Reply