I haven't been able to discover this information despite much searching.
We have a Flex 2 app that dynamically recompiles on the server when
the index.jsp is requested via an object/embed tag. The JSP requests
file.mxml.swf. Because the WEB-INF/flex directory contains the Flex 2
SDK, the app happily recompiles and works.
I'm trying to migrate the app to Flex 3 and I need to understand what
files need to go where for the app to dynamically recompile. A Flex 3
project template that dynamically recompiles would work. Or the
ability to create a new Flex 3 project that compiles on the server,
but this compilation option available under new Flex project is very
picky about being enabled and doesn't create the flex directory if you
get it to stay selected.
Comparing the 2.0.1 and 3.0.0 SDK directories doesn't help. The
deployed web app has
/WEB-INF
/flex <-- flex-config.xml; other -config.xml files
/frameworks <-- mx.swc
/frameworks_debug <-- mx_debug.swc
/jars <-- bunch of jars including flex.jar
/libs <-- bunch of swcs including charts.swc
/locale
/system_classes
/themes
/user_classes
and some other directories.
The Flex 2.0.1 sdks directory has
/frameworks <-- flex-config.xml and other stuff
/libs <-- bunch of swcs
/locale
/source
/themes
/lib <-- bunch of jars (similar to /flex/libs)
So there is plenty of overlap yet it's different enough to not be
drag-and-drop replaceable. In particular I'm not sure where the
mx.swc comes from, or the debug mx_debug.swc version.
Bottom line, I'm looking for a Flex 3 project that compiles
dynamically when deployed under a web app server, or information
towards that end. Thanks for any help.