Webmaster Forum / ColdFusion / Advanced Techniques / March 2008

A co-worker and I have been wrestling with this for a day and a half now, and
not sure why it's so difficult to find valid information on it. Basically,
we're trying to get BlazeDS working with ColdFusion 8, to access CFCs. The
basic word we've heard from Adobe is 'it works,' but no one is saying how. I'll
reference this conversation that someone had with Tom Jordahl over on the Labs
Forum:


http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=66
7&threadid=1324193&highlight_key=y&keyword1=coldfusion

So, after reading that post I went through the pdf, and the flash remoting
updater link (unnecessary). The final link was invalid, so I went to the cf8
livedocs and found the areas dealing with the flex2gateway.

There's way too much confusion in all of this. Our first real reference was in
the BlazeDS release notes:


http://labs.adobe.com/wiki/index.php/BlazeDS:Release_Notes#Integrating_BlazeDS_w
ith_a_ColdFusion_8_installation

This got it integrated, to a point. The first thing we notice here is the
removal of the data-management-config.xml, which is the only config area (that
we know of) where you can define a component for a destination (sort of
required). It looks like it may be possible to configure an event gateway, but
that could get counterproductive if you need a lot of small apps. I'm also not
finding much of anything on how to set some of these configurations at runtime,
rather than directly in the server configs. That makes anything developed very
unportable.

Tom, it isn't very clear cut. At all.

What might be making things especially difficult, on our part, is that we are
attempting to write an HTML AIR application that uses the Flex Ajax Bridge to
communicate with BlazeDS. The JS libraries have Consumer and Producer objects,
to which you can seemingly programmatically define channels and destinations
(to a degree). They do not, on the other hand, have a RemoteObject object,
which is the only (Flex) object I know of that lets you define a 'source'
attribute.

If we can ever figure this out we'll probably have a great Dev Center article.
I'm hoping that some of our troubles are just documentation issues relating to
it only recently coming out of beta. If anyone can shed some light on our
questions, your help would be greatly appreciated.