Skip to main content
Participant
July 14, 2010
Question

Project environments (development, staging, production) and modular application development

  • July 14, 2010
  • 1 reply
  • 613 views

Hey,

seeing the early status for the Module/Integration-libraries, have any of you already derived a way to handle team-development for modular projects? Especially with different environments for the application to run in, requiring parameters (like the server to communicate to) to be dependent on the environment.

My "perfect solution" would include local development using Flash Builder 4 and the integrated facilities to run an application as a "Web application" using an embedded Tomcat in Flash Builder 4 as the backend to the UI/Flex project as well as staging/production environments where the compiled flex-project resides on the same machine as the backend that it's talking to.

Basically my question has two parts:

  1. How do you configure your application (if at all) to change central parameters for your application according to the environment (e.g. the server url, or the path to modules which are loaded at runtime)
  2. How do you integrate that into the local Flash Builder workflow, which launches your application using a local URL

I'd love to hear your experiences with this, I'll report back if I established a structure I think worth sharing

best Jonas


P.S.: we're using Maven/Hudson for building and continuous integration, too, so those have some requirements themselves

This topic has been closed for replies.

1 reply

ledroff
Adobe Employee
Adobe Employee
July 21, 2010

What we do usually is the following :

* we have a <contextRoot>${my.web.context}</contextRoot> parameter in the flex app  pom.xml file

* we have linked resources in FlashBuilder to target and compile in the local webapp deployement folder