RE: [flexcoders] get rid of xml configuration in FDS, use JNDI
Considering how easy it is to manipulate xml files, it is really not that hard to add a step in the build process that automatically updates all your xml config files. Just a thought --Kelly -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of busitech Sent: Thursday, April 13, 2006 2:30 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] get rid of xml configuration in FDS, use JNDI I am evaluating FDS 2.0 for the first time, and am quite disappointed with the requirement of every single destination possible to be added to an XML file before it can be used... Adobe calls this software designed for the enterprise. However, with enterprise comes large applications, with hundreds or even thousands of objects, function calls, etc. I dread the thought of tediously adding all of our entities to an XML file, and maintaining another copy of function prototypes and API definition... We have developed a very nice workflow with Flash Remoting. We write EJB's, which get dropped into the server, which makes them immediately available to Flash Remoting through JNDI. It seems that FDS does not use JNDI? So another quasi-client layer for doing lookup and function calls is required? I see some nice features like data push (very cool), data queuing/sync for occasionally available services. But I'm not sure I'm willing to give up our efficient workflow for these features. I'm curious what others think about the scalability of having to lay out all of these XML files when developing an application. -- 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 -- 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/
Re: [flexcoders] get rid of xml configuration in FDS, use JNDI
But you have to restart the server to reload the config files. Dynamic destinations would be better than hard-coded static ones.-TomOn 4/13/06, Kelly @ Dekayd Media Inc. [EMAIL PROTECTED] wrote: Considering how easy it is to manipulate xml files, it is really not that hard to add a step in the build process that automatically updates all your xml config files. Just a thought --Kelly -Original Message- From: flexcoders@yahoogroups.com [mailto: flexcoders@yahoogroups.com] On Behalf Of busitech Sent: Thursday, April 13, 2006 2:30 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] get rid of xml configuration in FDS, use JNDI I am evaluating FDS 2.0 for the first time, and am quite disappointed with the requirement of every single destination possible to be added to an XML file before it can be used... Adobe calls this software designed for the enterprise. However, with enterprise comes large applications, with hundreds or even thousands of objects, function calls, etc. I dread the thought of tediously adding all of our entities to an XML file, and maintaining another copy of function prototypes and API definition... We have developed a very nice workflow with Flash Remoting. We write EJB's, which get dropped into the server, which makes them immediately available to Flash Remoting through JNDI. It seems that FDS does not use JNDI? So another quasi-client layer for doing lookup and function calls is required? I see some nice features like data push (very cool), data queuing/sync for occasionally available services. But I'm not sure I'm willing to give up our efficient workflow for these features. I'm curious what others think about the scalability of having to lay out all of these XML files when developing an application. -- 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 -- 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 . -- 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.
RE: [flexcoders] get rid of xml configuration in FDS, use JNDI
FDS deploy automaticaly config files when they change, no need to restart the server. -Original Message- From: flexcoders@yahoogroups.com on behalf of Tom Bray Sent: Fri 14-Apr-06 1:26 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] get rid of xml configuration in FDS, use JNDI But you have to restart the server to reload the config files. Dynamic destinations would be better than hard-coded static ones. -Tom On 4/13/06, Kelly @ Dekayd Media Inc. [EMAIL PROTECTED] wrote: Considering how easy it is to manipulate xml files, it is really not that hard to add a step in the build process that automatically updates all your xml config files. Just a thought --Kelly -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of busitech Sent: Thursday, April 13, 2006 2:30 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] get rid of xml configuration in FDS, use JNDI I am evaluating FDS 2.0 for the first time, and am quite disappointed with the requirement of every single destination possible to be added to an XML file before it can be used... Adobe calls this software designed for the enterprise. However, with enterprise comes large applications, with hundreds or even thousands of objects, function calls, etc. I dread the thought of tediously adding all of our entities to an XML file, and maintaining another copy of function prototypes and API definition... We have developed a very nice workflow with Flash Remoting. We write EJB's, which get dropped into the server, which makes them immediately available to Flash Remoting through JNDI. It seems that FDS does not use JNDI? So another quasi-client layer for doing lookup and function calls is required? I see some nice features like data push (very cool), data queuing/sync for occasionally available services. But I'm not sure I'm willing to give up our efficient workflow for these features. I'm curious what others think about the scalability of having to lay out all of these XML files when developing an application. -- 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 -- 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 developmenthttp://groups.yahoo.com/gads?t=msk=Web+site+design+developmentw1=Web+site+design+developmentw2=Computer+software+developmentw3=Software+design+and+developmentw4=Macromedia+flexw5=Software+development+best+practicec=5s=166.sig=L-4QTvxB_quFDtMyhrQaHQ Computer software developmenthttp://groups.yahoo.com/gads?t=msk=Computer+software+developmentw1=Web+site+design+developmentw2=Computer+software+developmentw3=Software+design+and+developmentw4=Macromedia+flexw5=Software+development+best+practicec=5s=166.sig=lvQjSRfQDfWudJSe1lLjHw Software design and developmenthttp://groups.yahoo.com/gads?t=msk=Software+design+and+developmentw1=Web+site+design+developmentw2=Computer+software+developmentw3=Software+design+and+developmentw4=Macromedia+flexw5=Software+development+best+practicec=5s=166.sig=1pMBCdo3DsJbuU9AEmO1oQ Macromedia flexhttp://groups.yahoo.com/gads?t=msk=Macromedia+flexw1=Web+site+design+developmentw2=Computer+software+developmentw3=Software+design+and+developmentw4=Macromedia+flexw5=Software+development+best+practicec=5s=166.sig=OO6nPIrz7_EpZI36cYzBjw Software development best practicehttp://groups.yahoo.com/gads?t=msk=Software+development+best+practicew1=Web+site+design+developmentw2=Computer+software+developmentw3=Software+design+and+developmentw4=Macromedia+flexw5=Software+development+best+practicec=5s=166.sig=f89quyyulIDsnABLD6IXIw -- YAHOO! GROUPS LINKS - Visit your group flexcodershttp://groups.yahoo.com/group/flexcoders on the web. - To unsubscribe from this group, send an email to: [EMAIL PROTECTED][EMAIL PROTECTED] - Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/. -- -- 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
Re: [flexcoders] get rid of xml configuration in FDS, use JNDI
I was actually pleasantly surprised when topic appeared in the group. Needless to say we are using custom gateways - not quite for JNDI vs XML - as I fail to see advantages of one over the other. For me custom gateway via flash remoting is more about different things like: 1. Ability to hot deploy new services - no recompile or references in SWF file - withautomatic distribution of the new AS classes to the Flex application as needed 2. Better control of the requests flow - making them "serial" rather then random 3. Transaction support by combining multiple requests/dataservices 4. Integration points for other technologies (PHP, .NET) As such the fact that people actively exploring custom gateways for Flex are good news as it really opens up number of integration and deployment techniques Thank you, Anatole - Original Message - From: Kelly @ Dekayd Media Inc. To: flexcoders@yahoogroups.com Sent: Thursday, April 13, 2006 8:13 PM Subject: RE: [flexcoders] get rid of xml configuration in FDS, use JNDI Considering how easy it is to manipulate xml files, it is really not thathard to add a step in the build process that automatically updates all yourxml config files.Just a thought--Kelly-Original Message-From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] OnBehalf Of busitechSent: Thursday, April 13, 2006 2:30 PMTo: flexcoders@yahoogroups.comSubject: [flexcoders] get rid of xml configuration in FDS, use JNDII am evaluating FDS 2.0 for the first time, and am quite disappointed with the requirement of every single "destination" possible to be added to an XML file before it can be used...Adobe calls this software "designed for the enterprise." However, with enterprise comes large applications, with hundreds or even thousands of objects, function calls, etc. I dread the thought of tediously adding all of our entities to an XML file, and maintaining another copy of function prototypes and API definition...We have developed a very nice workflow with Flash Remoting. We write EJB's, which get dropped into the server, which makes them immediately available to Flash Remoting through JNDI. It seems that FDS does not use JNDI? So another quasi-client layer for doing lookup and function calls is required?I see some nice features like data push (very cool), data queuing/sync for occasionally available services.But I'm not sure I'm willing to give up our efficient workflow for these features.I'm curious what others think about the scalability of having to lay out all of these XML files when developing an application.--Flexcoders Mailing ListFAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txtSearch Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- 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 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.
