BlazeDS requires Flex 3 – No official support for Flex 2
Filed Under (Flex, RIA, Technology) by jonr on January-29-2008

I have been playing a bit with BlazeDS, the new open source release of Adobe LiveCycle Data Services. Overall, it looks good to me, as the open source release has all the features I need. Unfortunately, I stumbled onto the fact that Flex 2 SDK doesn’t work with the BlazeDS messaging features, and I have a small project where I can’t upgrade to Flex 3.

When trying to produce a message the following fault is thrown:

“Destination ’simple-topic’ requires FlexClient support which was introduced in version 2.5. Please recompile the client application with an updated client framework.”

There isn’t actually a 2.5 version of Flex SDK. So, I enlisted some help from Adobe’s James Ward. He did some digging with the Flex engineering team, and after sometime was able to provide me with a work around. However, with that work around came the clarification that ‘BlazeDS is not compatible with Flex 2.’ I was in the dark to this fact and don’t believe that Adobe is publicizing it. I am ok with BlazeDS not supporting Flex 2 (it sounds like the next version of LCDS will have the same limitation), but I wish Adobe would have told me this up front. :)

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn
(7) Comments    Read More

Comments:
Eric Cancil on January 29th, 2008 at 12:25 pm #

Hi, I’ve tried looking but fail to find (or perhaps understand) the difference between BlazeDS, and LCDS. Is it simply a support difference, or are there feature differences?
-Eric

Dusty on January 29th, 2008 at 2:21 pm #

I’m pretty sure there were some changes in AMF3 with the release of Flex3. I say this because the Charles HTTP Proxy (awesome way to debug flexserver communications) doesn’t support BlazeDS in the current version. The author is on the ball, and has a beta with BlazeDS support, and should be released soon.

As for what changed, I have no clue, but it’s obvious something did

Tom Jordahl on March 3rd, 2008 at 2:34 pm #

You can use Flex 2.0.1 hotfix 2 or Flex 3 with BlazeDS 3. The “2.5″ in the message refers to LiveCycle Data Services 2.5, which was shipped requiring a hotfix (#2) for the compiler/SDK.

The AMF3 protocol did not change. The remoting and proxy services interoperate without issue between Flex 2 and BlazeDS.

However, the messaging and data management service implementations on the server required several core changes in channel/endpoint handshaking and in how messages are queued and routed to subscribers that are not backwards compatible with clients compiled against the ORIGINAL Flex 2 client library. This is a low level incompatibility, so previous messaging and data management code doesn’t need to be altered or edited in any way. You just need to recompile your app against the hotfixed Flex 2 or Flex 3 SDK.

Hope that clears it up a bit.

venkat on August 2nd, 2008 at 5:49 am #

Hi,

I am facing the same issue.
Can you please let me know how to work around it??

Bad of adobe , by the way..

jonr on August 9th, 2008 at 9:18 pm #

My understanding is there is no work around, but to use Flex 3 if you want to use BlazeDS.

Oleg on March 9th, 2010 at 1:46 pm #

Is there any solution yet?

jonr on March 10th, 2010 at 11:39 am #

Honestly, I doubt it. If you are still using Flex 2, it’s probably worth the pain to upgrade.

Post a comment
Name: 
Email: 
URL: 
Comments: