Specifications

169ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
compc -source-path .
-output c:/jrun4/servers/flex2/flex/WEB-INF/flex/user_classes/MyButtons.swc
-namespace http://acme2006AcmeManifest.xml
-namespace http://mynamespace SimpleManifest.xml
-include-namespaces http://acme2006 http://mynamespace
In this case, all components in both the http://mynamespace and http://acme2006 namespaces are targeted and
included in the output SWC file.
In a configuration file, these options appear as the following example shows:
<compiler>
<source-path>
<path-element>.</path-element>
</source-path>
<output>c:/jrun4/servers/flex2/flex/WEB-INF/flex/user_classes/MyButtons.swc</output>
<namespaces>
<namespace>
<uri>http://acme2006</uri>
<manifest>AcmeManifest.xml</manifest>
</namespace>
<namespace>
<uri>http://mynamespace</uri>
<manifest>SimpleManifest.xml</manifest>
</namespace>
</namespaces>
</compiler>
<include-namespaces>
<uri>http://acme2006</uri>
<uri>http://mynamespace</uri>
<include-namespaces>
In your MXML application, you define both namespaces separately:
<?xml version="1.0"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
xmlns:simple="http://mynamespace" xmlns:acme="http://acme2006">
<simple:SimpleComponent/>
<acme:AcmeComponent/>
</mx:Application>
You are not required to include all namespaces that you define as target namespaces. You can define multiple
namespaces, but use only one target namespace. You might do this if some components use other components
that are not directly exposed as MXML tags. You cannot then directly access the components in the unused
namespace, however.
The following command line example defines two namespaces, http://acme2006 and
http://mynamespace, but only includes one as a namespace target: