RE: [flexcoders] Re: FDS Beta 3 with ColdFusion Issues

[Bill Sahlas]

You need to enable the logging filters DataService.coldfusion, Message.coldfusion.  Refer to flex-enterprise-services.xml in the C:\fds2\resources\config folder for all the sample configs attributes.  Flex can watch certain configs files for changes and will redeploy the ‘web-app’ whose file was changed (could be /samples, /flex, /flex-admin, /foo).  The list of files is found in the /WEB-INF/flex/flex-enterprise-services.xml file for every web-app       <system>         <redeploy>             <enabled>true</enabled>             <watch-interval>20</watch-interval>             <watch-file>{context.root}/WEB-INF/flex/flex-enterprise-services.xml</watch-file>             <watch-file>{context.root}/WEB-INF/flex/flex-proxy-service.xml</watch-file>             <watch-file>{context.root}/WEB-INF/flex/flex-remoting-service.xml</watch-file>             <watch-file>{context.root}/WEB-INF/flex/flex-message-service.xml</watch-file>             <watch-file>{context.root}/WEB-INF/flex/flex-data-service.xml</watch-file>             <touch-file>{context.root}/WEB-INF/web.xml</touch-file>         </redeploy>     </system>     If you change a destination attribute in your /foo/WEB-INF/flex/flex-data-service.xml and you’ve got the <redeploy> params specified in your flex-enterprise-services.xml file then your /foo web-app will redeploy.  Your application when creating the DataServices object needs to pass in the destination name so that’s another place to check. There are only a couple of places where this could brake down.   You have the yourapp.mxml(.as) file that defines the DataServices object you have the flex-enterprise-services.xml file that needs tweaking (see C:\fds2\resources\config folder for samples) you have the flex-data-service.xml file that contains the destination   In order for your application (mxml/as) to know about the new destinations it must recompile before the web-app redeploys your {context.root}/WEB-INF/flex/flex-data-service.xml file   Clear your web cache; make sure the swf is being rebuilt   HTH, Bill   From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Nikmd23 Sent: Friday, May 12, 2006 10:35 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: FDS Beta 3 with ColdFusion Issues   I dug a little deeper into this issue, and this is what I've found: My destination works, I named it "testDest" and now I can connect to it fine.  I changed it's name to "otherTest", restarted Flex Server, changed my MXML to point to it, and when I ran it, it said that "otherTest" was not found. I figured there was some kind of a cache problem, so I restarted my computer.  Once it booted up, I started Flex Server, and re-ran my MXML.  Same problem, "otherTest" not found. So then, I opened up the XML file, changed the destinations name back to "testDest", changed my MXML to point to that destination and re-ran again (WITHOUT restarting Flex Server).  And it worked fine. So Flex Server seems to have an issue with changes in destinations.  Restarting the server/machine doesn't seem to help, and unlike in Beta 2, the counsel output doesn't seem to tell you what destinations it has defined. The Flex Admin app (http://localhost:8700/flex-admin/) does seem to tell you which destinations are defined, and in each case, the proper destination is defined there. Even when I get the error. Is this a know bug in Flex Server, or is there another service somewhere I should be restarting? -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Web site design development Computer software development Software design and development Macromedia flex Software development best practice YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.