The only problem that I see running seperated instances of FDS & CFMX is the 
fact that FDS doesn't ship with the remoting for CF so when you define CF 
remoting destinations(the "ColdFusion" one) it throws an error, so to be able 
to use a mix of remoting + data management you'll have to keep 2 xml files, one 
for FDS and one for compilation. If there is another way, I didn't find any 
documentation about it.

I have it running CFMX7+ FDS and now without issues but more documentation 
about this would be nice.

One of the issues about the technote is the fact that FDS and CFMX7 both uses a 
MessageBrokerServlet definition. I kept the CF (the Flex one couldn't load 
those CF remoting Classes)

João Fernandes

-----Original Message-----
From: flexcoders@yahoogroups.com on behalf of Jim
Sent: Thu 06-Jul-06 7:54 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: FDS on CFMX configuration problems
 
I tried the same thing (combining FDS with CFMX 7.0.2) using the 
same technote and wasn't able to get it to work. I emailed an 
insider at Adobe on the Coldfusion team I met at the CFObjective 
conference and learned that they aren't very happy with that 
technote and recommended that I run FDS and CFMX separately for now.

I haven't tried that yet, but apparently you did and it was 
working, which is encouraging to me. I've spent three days trying to 
get FDS working with a fresh installation of CFMX 7 Multiserver
(JRun4) option. The WEB-INF directory installs in the nested 
directories within the JRun4 folder, but the new CF/Flex Wizard 
expects the WEB-INF to be in the webroot.

I've been having issues with the services-config.xml file. I found a 
copy of the file Ben Forta uses on the sys-con website which has 
worked so far.

But if you manage to combine FDS and CFMX 7 and get them working, 
please share what you did.

Thanks,

Jim Pickering

--- In flexcoders@yahoogroups.com, "Tom Bray" <[EMAIL PROTECTED]> wrote:
>
> When I first started working with FDS, I used the standalone 
version with
> integrated JRun and had FB configured to launch FDS and direct its 
logging
> to the output pane in FB.  I was happy.
> 
> Now, I'm trying to configure FDS on top of CFMX and haven't had 
much
> success.  I used the instructions below at this link:
> http://www.adobe.com/cfusion/knowledgebase/index.cfm?
id=4f079a4d&pss=rss_flex_4f079a4d.
> It would be very helpful if Adobe would expand upon those 
instructions with
> the steps for getting the sample apps up and running.
> 
> Also, the instructions for setting up debugging (
> 
http://labs.adobe.com/wiki/index.php/Flex_Enterprise_Services:Debuggi
ng)
> need to be updated for the final release of FDS and I'd love to 
see a
> similar document for setting up debugging with FDS on CFMX.
> 
> In the meantime, I'm having errors that I don't know how to get 
additional
> information on.  I'm trying to get the notes sample app running, 
and I get
> this error:
> 
> [RPC Fault faultString="Send failed" 
faultCode="Client.Error.MessageSend"
> faultDetail="Channel.Connect.Failed error 
NetConnection.Call.Failed: HTTP:
> Status 500"]
> 
> Subscribing to the notes destination works, but sending a message 
doesn't.
> I obviously need more details to diagnose the problem, so an 
explanation of
> how to see that logging information would be awesome.
> 
> Thanks,
> 
> Tom
>








------------------------ Yahoo! Groups Sponsor --------------------~--> 
Great things are happening at Yahoo! Groups.  See the new email design.
http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~-> 

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

<<winmail.dat>>

Reply via email to