<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: BlazeDS requires Flex 3 – No official support for Flex 2</title>
	<atom:link href="http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/</link>
	<description>Enterprise Software Consultant</description>
	<lastBuildDate>Mon, 15 Mar 2010 20:02:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jonr</title>
		<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/comment-page-1/#comment-21336</link>
		<dc:creator>jonr</dc:creator>
		<pubDate>Wed, 10 Mar 2010 18:39:52 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=18#comment-21336</guid>
		<description>Honestly, I doubt it.  If you are still using Flex 2, it&#039;s probably worth the pain to upgrade.</description>
		<content:encoded><![CDATA[<p>Honestly, I doubt it.  If you are still using Flex 2, it&#8217;s probably worth the pain to upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oleg</title>
		<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/comment-page-1/#comment-21335</link>
		<dc:creator>Oleg</dc:creator>
		<pubDate>Tue, 09 Mar 2010 20:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=18#comment-21335</guid>
		<description>Is there any solution yet?</description>
		<content:encoded><![CDATA[<p>Is there any solution yet?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonr</title>
		<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/comment-page-1/#comment-20447</link>
		<dc:creator>jonr</dc:creator>
		<pubDate>Sun, 10 Aug 2008 04:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=18#comment-20447</guid>
		<description>My understanding is there is no work around, but to use Flex 3 if you want to use BlazeDS.</description>
		<content:encoded><![CDATA[<p>My understanding is there is no work around, but to use Flex 3 if you want to use BlazeDS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: venkat</title>
		<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/comment-page-1/#comment-20444</link>
		<dc:creator>venkat</dc:creator>
		<pubDate>Sat, 02 Aug 2008 12:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=18#comment-20444</guid>
		<description>Hi,

I am facing the same issue.
Can you please let me know how to work around it??

Bad of adobe , by the way..</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I am facing the same issue.<br />
Can you please let me know how to work around it??</p>
<p>Bad of adobe , by the way..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Jordahl</title>
		<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/comment-page-1/#comment-8839</link>
		<dc:creator>Tom Jordahl</dc:creator>
		<pubDate>Mon, 03 Mar 2008 21:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=18#comment-8839</guid>
		<description>You can use Flex 2.0.1 hotfix 2 or Flex 3 with BlazeDS 3.  The &quot;2.5&quot; 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&#039;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.</description>
		<content:encoded><![CDATA[<p>You can use Flex 2.0.1 hotfix 2 or Flex 3 with BlazeDS 3.  The &#8220;2.5&#8243; in the message refers to LiveCycle Data Services 2.5, which was shipped requiring a hotfix (#2) for the compiler/SDK.</p>
<p>The AMF3 protocol did not change. The remoting and proxy services interoperate without issue between Flex 2 and BlazeDS.</p>
<p>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&#8217;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.</p>
<p>Hope that clears it up a bit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dusty</title>
		<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/comment-page-1/#comment-6076</link>
		<dc:creator>Dusty</dc:creator>
		<pubDate>Tue, 29 Jan 2008 21:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=18#comment-6076</guid>
		<description>I&#039;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&#039;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&#039;s obvious something did</description>
		<content:encoded><![CDATA[<p>I&#8217;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&#8217;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.</p>
<p>As for what changed, I have no clue, but it&#8217;s obvious something did</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Cancil</title>
		<link>http://gorillajawn.com/wordpress/2008/01/29/blazeds-requires-flex-3-%e2%80%93-no-official-support-for-flex-2/comment-page-1/#comment-6072</link>
		<dc:creator>Eric Cancil</dc:creator>
		<pubDate>Tue, 29 Jan 2008 19:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=18#comment-6072</guid>
		<description>Hi, I&#039;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</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;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?<br />
-Eric</p>
]]></content:encoded>
	</item>
</channel>
</rss>
