Several things, including ports, server names. Not often context
roots, but certainly debugging levels.
The way we worked around it was to declare end-points in our mxml
which over-rode the channels' end-points. This is ok, but it is a
bit of a config hack, since we couldn't configure from flexvars or
server-supplied configuration properties or anything.
But regardless, we're still in the position where if we have a
developer on one computer create a project, that project has to have
knowledge of a web-app project. It can't resolve the target flex-
config or messaging stuff relatively, or from an eclipse variable.
So either all developers have to have an identical setup (not
possible in our environment) or we have to have developers constantly
accidentally checking-in FB project settings and overwriting them as
they point the FB to their local webapp location.
I'm not entirely clear on why an FB project even needs this. The
config files should be supplied, of course, but Flex Builder is being
needlessly picky about the structure of things. Since the command-
line app can hit against an arbitrary flex-config.xml, why shouldn't
the FB?
regards,
christian.
On Mar 21, 2007, at 10:59 AM, Peter Farland wrote:
What sorts of things change between your dev, qa, staging and
production environments? Debugging levels? Ports? WAR context roots?
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Christian Gruber
Sent: Wednesday, March 21, 2007 10:52 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] FDS 2 becomes LDS 2.5 | See labs.adobe.com
Does LCDS and the FlexBuilder update allow for more indirect
configuration of things like the web-app config location, or the
channel locations? We've had a really hard time configuring things
so we can build a single binary on our build server, and test that
same binary in our dev, QA, staging and production environments.
Without the ability to certify a build through staged environments,
Flex will have a difficult time rolling out in large organizations
with serious software development processes in place.
regards,
Christian.
On Mar 21, 2007, at 9:54 AM, Peter Farland wrote:
Note that updates to the Flex SDK and FlexBuilder will soon be
available to support LCDS 2.5 (which is still in Beta).
.
christian gruber + [EMAIL PROTECTED] + bus 905.640.1119 + mob
416.998.6023
process coach and architect + ISRAFIL CONSULTING SERVICES
christian gruber + [EMAIL PROTECTED] + bus 905.640.1119 + mob
416.998.6023
process coach and architect + ISRAFIL CONSULTING SERVICES
