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 - with automatic 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 -----
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 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: [email protected]
[mailto:[EMAIL PROTECTED] On
Behalf Of busitech
Sent:
Thursday, April 13, 2006 2:30 PM
To: [email protected]
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
