Ant task to include Halo theme

Hi,
I recently migrated from Flex 3.4 to Flex 4. Everything works fine when I compile the application using Flash Builder 4. But I am having issues making our automated ant builds pick up the Halo theme over the Spark theme.
In FB4, I just used the "Flex Theme" options under Project -> Properties to define the Halo theme as the default theme.Before that I used the -theme compiler argument. Both work fine.
For our ant task, I tried adding:
<compiler.theme dir="${FLEX_HOME}/frameworks" append="false">
<include name="/themes/Halo/halo.swc" />
</compiler.theme>
Unfortunately that does not seem to work and the result still shows the Spark theme. I also tried making "theme" a task attribute and the other options according to Flex 4 docs ( http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7a63.html ), but to no avail.
I have very limited experience with ant and would appreciate some input.
Thanks!

I just ran into this same issue yesterday, Here's what worked for me, placed between the <mxmlc> </mxmlc> tags
<theme dir="${FLEX_HOME}/frameworks/themes/Halo">
<include name="halo.swc" />
</theme>

Similar Messages

MXMLC ANT task not including AIR libraries

Hi Guys,
This is the MXMLC ant task which I am using the compile my test app. If i set the static-link-runtime-shared-libraries="true" , the AIR libraries gets merged into my output swf. But when this attribute is set to false, I dont see the AIR libraries added to my SWF file. As a result when I run the AIR version fo my project, I dont see the application launch right. I have so many RSL in my project and I wanted to have static-link-runtime-shared-libraries="false". Is there a way to have AIR libraries include in my output file and still have this static-link-runtime-shared-libraries="false".
<mxmlc
 file="${project.name}/src/Test.mxml"
 output="${build.mxmlc.dir}/Test.swf"
 static-link-runtime-shared-libraries="true"
 >
 <load-config filename="${air.config}"/>
 <source-path path-element="${project.name}/src" />
 <source-path path-element="${flex.frameworks.dir}/libs/air"/>
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/framework.swc">
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swz"/>
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/datavisualization.swc">
 <url rsl-url="${rsl.dir}/datavisualization_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 </mxmlc>
My RSL are compiled using COMPC task and the AIR libraries are included into them using the below attributes of compc task.
<source-path path-element="${basedir}/src" />
<source-path path-element="${flex.frameworks.dir}/projects/airframework/src" />
<source-path path-element="${flex.frameworks.dir}/projects/air/ServiceMonitor/src" />
I am really stuck with this problem and not able to get my release build launch right. Again, any light on this problem will be of great help.!

 <mxmlc
 file="${project.name}/src/Test.mxml"
 output="${build.mxmlc.dir}/Test.swf"
 static-link-runtime-shared-libraries="true"
 >
 <load-config filename="${air.config}"/>
 <source-path path-element="${project.name}/src" />
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/framework.swc">
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swz"/>
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/datavisualization.swc">
 <url rsl-url="${rsl.dir}/datavisualization_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 </mxmlc>
This also seems to work. AIR libraries are included in my output SWF. It all happens right when I have static-link-runtime-shared-libraries="true" . Why? Why does that not work when i have static-link-runtime-shared-libraries="false" ??

Flex ant build - problem including custom theme

Hi,
I added custom ios theme using the below code in the flex ant build. The custom ios theme does not seem to be included.
<compiler.theme dir="${FLEX_HOME}/frameworks" append="true">
<include name="themes/Spark/spark.css" />
<include name="themes/Mobile/mobile.swc" />
</compiler.theme>
<compiler.theme dir="${deploy.dir}/lib" append="true"> <include name="mobiletheme_ios.swc" />
</compiler.theme>
I also tried using just <theme> tag but it did not help.
Hoping a solution with the forum's help.
Thanks in advance
<include name="themes/Halo/halo.swc" />

Sorry, I meant to address that. Yes, since we've moved up to the Flex 3 sdk, we are pointing at a new directory. The old directory was flex_sdk and the new directory is flex_sdk_340.
FLEX_HOME is being set in the build.properties file for local building and then overidden in the build.xml file with this code:
<target name="build">
 <available property="FLEX_HOME" value="/apps/flex_sdk_340" file="/apps/flex_sdk_340" />
 <echo>FLEX_HOME = ${FLEX_HOME}</echo>
 <antcall target="compile" />
</target>
I did notice a warning about not using the available property, so I removed it and just changed what FLEX_HOME was set to in the build.properties file to the server directory. Would mess up local building but regardless it didn't matter because it had no effect on the error being generated. I alos looked a little into the file property of the available tag trying to figure out if that was somehow an issue but I wasn't able to come to any conclusion.
Before the program errors out, it does displayt he echo statement and the value of FLEX_HOME appears to be correct in that it does show /apps/flex_sdk_340.
Thank you so much for your continued help. This is truly frustrating because nothing but a directory name has really changed and yet it stopped working. I can't find any information anywhere on what could be wrong and this is really my last resort.

FlexUnit Ant task freeze at Reciving Data...

Hello,
I'm trying to use flex unit task and when I run it, get this on console and stay there for ever.
"*****" is just to privacy
this is my ant task
<target name="UNIT TEST">
 <echo>COMPILING TEST SWF..</echo>
 <mxmlc output="${basedir}/bin/Test.swf" file="${basedir}/test-src/TestRunner.as">
 <target-player>${env.TARGET_PLAYER}</target-player>
 <load-config filename="${FLEX_HOME}/frameworks/flex-config.xml"/>
 <source-path path-element="${FLEX_HOME}/frameworks"/>
 <compiler.library-path dir="${FLEX_HOME}/frameworks" append="true">
 <include name="libs" />
 <include name="../bundles/{locale}" />
 </compiler.library-path>
 <source-path path-element="${env.WIP_CLIENT_COM_SRC_PATH}"/>
 <define name="CONFIG::FLASH_AUTHORING" value="false"/>
 <source-path path-element="${basedir}/test-src"/>
 <source-path path-element="${basedir}/src"/>
 <compiler.library-path dir="${basedir}" append="true">
 <include name="libs" />
 </compiler.library-path>
 <compiler.library-path dir="${env.WIP_CLIENT_COM_SRC_PATH}" append="true">
 <include name="libs" />
 </compiler.library-path>
 <compiler.external-library-path dir="${env.WIP_CLIENT_COM_SRC_PATH}/libs" append="true">
 <include name="GenericChat.swc"/>
 </compiler.external-library-path>
 </mxmlc>
 <echo>COMPILED TEST SWF..</echo>
 <echo>Running Test Runner SWF</echo>
 <flexunit swf="${basedir}\bin\Test.swf"
 toDir="${basedir}\bin"
 haltonfailure="true"
 verbose="true"
 localTrusted="false"/>
 <echo>Ran Test Runner SWF</echo>
 <echo>Generate Readable Tests</echo>
 <junitreport todir="${basedir}\bin">
 <fileset dir="${basedir}\bin">
 <include name="TEST-*.xml"/>
 </fileset>
 <report format="frames" todir="${basedir}\bin\html"/>
 </junitreport>
 <echo>Generated Readable Tests</echo>
 </target>
Buildfile:******.xml
UNIT TEST:
 [echo] COMPILING TEST SWF..
 [mxmlc] Cargando el archivo de configuración D:\Desarrollo\fdk\flex_sdk_4.5.1.21328\frameworks\flex-config.xml
 [mxmlc] D:\Proyectos\Bubble\Cliente\trunk\test-src\TestRunner.as: Advertencia: Esta unidad de compilación no tiene ninguna factoryClass especificada en los metadatos del fotograma para cargar las bibliotecas compartidas en tiempo de ejecución configuradas. Para compilar sin bibliotecas compartidas en tiempo de ejecución establezca la opción -static-link-runtime-shared-libraries en true o elimine la opción -runtime-shared-libraries.
 [mxmlc] *********Test.swf (50729 bytes)
 [echo] COMPILED TEST SWF..
 [echo] Running Test Runner SWF
[flexunit] Validating task attributes ...
[flexunit] Generating default values ...
[flexunit] Using default working dir [****]
[flexunit] Using the following settings for the test run:
[flexunit] FLEX_HOME: [*****fdk\flex_sdk_4.5.1.21328]
[flexunit] haltonfailure: [true]
[flexunit] headless: [false]
[flexunit] display: [99]
[flexunit] localTrusted: [false]
[flexunit] player: [flash]
[flexunit] port: [1024]
[flexunit] swf: [****\Test.swf]
[flexunit] timeout: [60000ms]
[flexunit] toDir: [********\bin]
[flexunit] Setting up server process ...
[flexunit] Starting server ...
[flexunit] Opening server socket on port [1024].
[flexunit] Waiting for client connection ...
[flexunit] Executing 'rundll32' with arguments:
[flexunit] 'url.dll,FileProtocolHandler'
[flexunit] '********\Test.swf'
[flexunit] The ' characters around the executable and arguments are
[flexunit] not part of the command.
[flexunit] Client connected.
[flexunit] Setting inbound buffer size to [262144] bytes.
[flexunit] Receiving data ...
Thank you in advance.
Javier

I still have not been able to get FlexUnit running with AIR SDK 15. But I found a workaround:
Compile the source code with SDK 15 into swc files.
Set FlexUnit to use SDK 4.
Do not include source code in the FlexUnit Ant task.
Include the swc files in stead by adding another library dir parameter to the flexunit call.

How to include assigned .as files in MXMLC ant task ?

When i use mxmlc ant task, i found that
the tag <include-sources/> doesn't support !
( described by http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7a63.html )
neither SDK version 3.x nor 4.x
Are they lying?!
How to include assigned .as files ?
Thank you !

My understanding is that mxmlc will use all available resources in the source path, as needed. Instead of giving it individual resources to include, you simply need to give it the source-path that contains those resources. This is different from a library project, which may need to include individual classes that are never used in that library.

Are the Flex Ant tasks open source? If so, where to find them?

I took a brief look into Flex SDK source and didn't see the Flex Ant tasks. Is this also open source? Where would I find it?
I probably won't change anything, just want to take a look. Although, I'm annoyed that the tasks don't work in a similar fashion as the core ant tasks
Thanks.

http://opensource.adobe.com/svn/opensource/flex/sdk/trunk/modules/antTasks
Note that the way the tasks are put together ain't exactly pretty--they're just a very thin wrapper on mxmlc / compc / etc. There are some advantages to this approach, but if you're hoping to learn about the compiler options by looking at the task source, it could take some doing.

Are the WLS 9.1 Web Service Ant Tasks ready for prime time?

I am trying to create a Proof of Concept (POC) for Enterprise and B2B Services at Wendy's Int'l, Inc.
As part of this POC, I created a WSDL for an in-house service and then used the wsdlc and jwsc Ant Tasks to translate this WSDL to Java classes and ultimately (I hoped) a deployable services.
In this document, I describe the issues I encountered setting up what I consider to be a simple POC.
I'll try to attach my WSDL file and build.xml so you can follow along.
I'll also try to attach my CSS file so you can compare how the generated WSDL appears in the Browser to the way I want it to appear.
If attachments are not allowed on these forums, then I will wait and see if there is interest in those documents before I paste them under this topic.
Some preliminary information about my environment.
Environment:
 Windows XP Pro SP2
 WebLogic 9.1
 Java 1.5.0_04
Service Name:
 AppRelease
Note: If I modify my WSDL (perhaps to add a new Operation or to change the definition of an element) and run wsdlc again, the AppReleaseSOAPPortImpl.java file is overwritten For this reason, I implemented my service logic in a class called AppReleaseServiceImple.java.
Now, for the issues.
1. Bug:
In the WSDL generated by wsdlc, the wsdl:part child of the wsdl:message tag is erroneously prefixed with a colon.
This occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
2. Bug:
In the WSDL generated by wsdlc, the wsdl:input and wsdl:output children of the wsdl:operation child of wsdl:portType tag are erroneously prefixed with a colon. Like 1 above, this occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
The error message generated by Bugs 1 and 2 is not helpful in diagnosing the problem:
[jwsc] Error at line:46 col:7 ':' expected [?! -- [CDATA[ ]
3. Bug:
In the WSDL generated by wsdlc, the documentation elements have all of my html elements stripped out, as well as my xhtml and wsdl namespace references. This completely negates one of the best features of the documentation tag, being able to present the WSDL in a browser as a nicely formatted, human friendly document which is also the underlying WSDL that can be viewed when the person views the source document.
I label this as a bug because it greatly reduces the functionality of the resulting WSDL.
4. Annoyance:
The WSDL generated by wsdlc has all of my comments stripped out, except the comments in the xsd:schema section of the wsdl:types element. I would prefer that all my comments be left in the WSDL, but if comments must be stripped out then I think all of the comments should be stripped out.
5. Annoyance:
The WSDL generated by wsdlc has my CSS specification stripped.
Work around: I donâ€™t know if adding the CSS back will do any good because I have not yet created a deployable service (see the last issue below).
6. Annoyance:
The WSDL generated by wsdlc has different namespace prefixes than the ones I specified for my application's namespace and for the http://schemas.xmlsoap.org/wsdl/soap/ namespace.
Work around: Perform a find/replace on namespace prefixes "s0" and "s1" to return them to my prefered values.
Another thing I can do at this point is simply replace the generated WSDL in the jar file with my original WSDL. This would address issues 1 thru 6 above.
7. Annoyance:
The java source files created by wsdlc are put into a jar file. This makes it annoying when working within a traditional IDE like Eclipse because there is no way to reference the source files within the jar as working source.
Work around: Extract the source files from the jar and identify the resulting directory structure as part of the source structure of the project.
8. Bug:
The jwsc task complains if the same parameter name is used in multiple operations. I received the following Errors from jwsc:
[jwsc] C:\IDE\workspace\Acre-WL9.1\AppReleaseSOAPPort.java 0:0
[jwsc] [ERROR] - Parameter element "{http://acre.services.wendys.com/AppRelease/}garRequest" is not unique across document/literal bare WebService.
Since the operation names are unique, I see no reason to also require uniqueness in the parameter names used by those operations.
Work around: Use unique element names for the input parameters of the services operations.
9. Bug:
Once items 1, 2 and 8 above are taken care of, jwsc fails with the following error:
java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.ApplicationBeanImpl
This seems to be due to the weblogic.jar file not being in the System Classpath.
However, I should note that when I set verbose="on" and debug="on" in the jwsc ant task, there was a message from the task which stated "[jwsc] [search path for class files: [big freakinâ€™ jar list]". In the big freakinâ€™ jar list, I did find weblogic.jar and weblogic.jar has the required ApplicationBeanImpl. This indicates to me that the jwsc task does not fully honor either its classpathref attribute, nor an embedded classpath element.
Work around: Make sure the weblogic.jar is in the System Classpath.
10. Bug:
I fixed bug #9 by running a setDomainEnv script and then ran my ant task. This time I received the following output:
ant build-serviceBuildfile: build.xml
build-service:
[jwsc] 1 JWS files will be processed.
[jwsc] Processing JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java
[jwsc] JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java Validated.
[AntUtil.deleteDir] Deleting directory <some temporary directory>
BUILD FAILED
java.lang.ExceptionInInitializerError
At this point, I am completely stymied about how to proceed.
I wonder what new issues await once this 10th issue is addressed.
Really, is this tool set ready for prime time?

Sorry to hear you are having so many issues with using the WLS 9.1 web service Ant tasks, inside of Eclipse.
I generally create a User Library for the couple weblogic jars needed, and use it (the User Library) in my Eclipse projects that I create JWSes in. 
I also have a separate WebLogic Library in Eclipse (actually 2 libraries since I work with WL 8.1 and now WL 9.1). As you may know, one of the long-standing issues with the Ant integration within Eclipse is the fact that Ant, being an External Tool, does not receive the Project-specific Paths/Libraries. However, since most Java-relevant Ant tasks can take classpath and classpathref attributes, this is usually not an issue. In the case of the BEA-supplied wsdlc Ant task, it is apparent from the verbose/debug console output that wsdlc can see the jars in its classpathref, but it ignores those references when resolving class references and instead only uses the system classpath.

I've only needed the weblogic.jar and xbean.jar, not all the ones you mentioned in an earlier thread of this post. 
I have not tried to winnow down exactly which jars are required. I simply included all the jars that exist and were added to the system classpath by the setDomainEnv.bat file created by WebLogic 9.1.

Afterwards, I create an Ant Builder to build the JWS Web Service EAR, as opposed to fiddlin' with Eclipse. 
I too use Ant to build my deployable archives. Eclipse is simply my IDE of choice. I validated that all the issues I listed occurred when running Ant from the command line.

If you are interested in how I do it, send me an e-mail (to [email protected]), and I'll send you a zip of one of these JWS projects. The build.xml script for the project, takes care of a lot of the "annoyances" you mentioned, one of which I think is not accurate. I have never had a situation where the wsdlc Ant task "overwrote" my XXXImpl.java file.. 
Since I'm doing a POC to determine how we want to proceed with developing Web Services and an SOA in general, I tried to perform the same tasks using Axis 2 1.0, the WebLogic 9.1 tools, and XFire 1.1. Overwriting the Impl class is a common failing in the tools which take a WSDL and create Java source files for all three frameworks.

Try my scenario. Add another operation to an existing WSDL, and run the wsdlc Ant Task. The old IMPL class will be over-written.

Because of this, I have a separate Impl class and I make sure that all its methods and annotations match the methods and annotations in the Skeleton Impl class created by wsdlc.

Maybe that's because I use the <exec> Ant task with jar.exe (the xvf options) in my build.xml, to only get what I need out of the .jar/.zip the wsdlc generates. I'm typically only interest in the interface class that my XXXImpl.java file needs to implements, because I use XMLBeans for the input args (and return values) of my web service operations. 
Perhaps. I am not using XMLBeans in any of the three frameworks because the resulting service seems to be lighter-weight in all three frameworks if XMLBeans is not used. I'm sure there will be scenarios where XMLBeans is preferred, but I have not encountered that case in this POC.

Regards,
Mike Wooten
Thanks for the follow-up.
Mike McAngus

Can i reference external flex-config in flexunit ant task?

flexunit gurus,
i'm trying to figure out how to best specify the compiler arguments for the flexunit ant task in flexunit 4.1 beta 1. from the documentation i see this sample flexunit usage:
<flexunit workingDir="${bin.loc}" toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">
<testSource dir="${main.src.loc}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>
<library dir="${lib.loc}" />
</flexunit>
in this example, the source and library paths are explicitly listed. in this simple example all the needed libraries reside within a single directory.
when i build my application, i use a custom flex-config.xml file, as the following snippet shows:
 <mxmlc file="${application.file}" output="${swf.debug.file}" debug="true" headless-server="${headless.server}">
 <load-config filename="${flex.config.file}" />
 </mxmlc>
in that custom flex-config.xml file i list all the build options (e.g. source dirs, library paths, theme, etc.) appropriate for building the application. the libraries i reference are in a number of different directories (in general each 3rd party library is in a different directory).
in the flexunit task, i could individually reference all the same libraries that are in the flex-config.xml, but that'd be a pain to keep them in sync. i suppose i also could parse the flex-config.xml to extract the library information and use that to populate the library argument. really what i want to say in the flexunit task is "build all source and tests as indicated in flex-config.xml, then run the tests", perhaps with a syntax like the following:
<flexunit workingDir="${bin.loc}" toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">
 <load-config filename="${flex.config.file}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>
<library dir="${flexunit.lib}" />
</flexunit>
i'd rather keep the flex-config.xml file free of any test specific information, so ideally i'd specify the path to the flexunit swc's and the test path in the flexunit task (as in the above example).
is there support for such usage currently or planned for in the future? recommendations on how best to accomplish my goal of not duplicating library information already present in a custom flex-config.xml?
thanks.
-mike

hi brian,
thanks for your response.
i understand the desire to avoid re-implementing the flex sdk ant tasks. i'm not sure that can reasonably be accomplished wihen the TestRunner is dynamically generated from within the flexunit task. in addition to the source path and library path, the theme setting and namespaces settings can affect successful compilation, and the runtime-shared-library-path setting can affect whether the produced swf runs correctly.
perhaps there's an alternative. what if we separate the creation of the TestRunner.mxml from the compilation and the execution of the tests. if flexunit offers an ant task that can produce (but not run) a TestRunner.mxml, i can write the mxmlc task that compiles it properly, and then i can invoke the old style flexunit specifying the swf argument. this would still accomplish my primary goal of not needing to manually enumerate every test file in a TestRunner.mxml that i have to maintain (and which neither Flash Builder nor maven builds require). to compile the TestRunner.mxml, i'd load in my custom flex-config.xml, then append to the source path and library path to include my test directory and flexunit libraries.
maybe something like the following to create the TestRunner:
<generatetestrunner output="${bin.loc}/TestRunner.mxml">
 <testSource dir="${test.dir}">
 <include name="**/*Test.as" />
 </testSource>
</generatetestrunner>
thoughts?
one other thing i noticed about the current library argument to flexunit is that it assumes a directory even if you provide an explicit path to an swc (i tried switching <library dir...> to <library file...> but that didn't seem to make a difference). in my case, there are specific swc's i need in the library path, and the task assuming i mean a directory when i specify an explicit swc is problematic. the directory my swc libraries are contained in sometimes contain multiple and conflicting versions of a library (each library directory contains various snapshot builds of the library). i need a way to explicitly indicate which library to use.
finally, could you point me to the java source for the flexunit ant tasks? i've found the flexunit action script source ok but haven't found where the java ant task is defined.
thanks.
-mike

Java.lang.NullPointerException running flexunit ant task in 4.1 Beta 2

Hello,
After trying to debug this all day, I thought I would ask the community.
I am trying out the new FU4.1 Beta 2 (3.5) from the downloads page. We have a working CI system set up with 4.0, and I thought trying out 4.1 beta 2 would simply be a matter of replacing the binaries in my lib folder and re-running the ant script. Evidently not, or else I am missing something.
After updating to the 4.1 Beta 2 binaries, if I re-run a sample project in Eclipse, the build fails with a java NullPointerException when the <flexunit> ant task is invoked. We have an involved setup that uses the groovy AntBuilder and other esoteric constructs, so I thought I would create a very simple test script similar to the sample CI project to see if that would work. Unfortunately, I am still seeing the NPE. The worst part is that there is absolutely no debug information provided - no message, no traceback. I even attached the Ant source and debugged it. I could see the NPE being caught, but it contained a null message and null traceback.
Here is the simplified ant script:
<project name="tests" basedir=".">
 <target name="test-init" depends="">
 <mkdir dir="${build.dir}"/>
 <mkdir dir="${reports.dir}"/>
 <mkdir dir="${reports.xml}"/>
 <mkdir dir="${reports.html}"/>
 
 
 <flexunit
 swf="${build.dir}/TestRunner.swf"
 toDir="${reports.xml}"
 haltonfailure="false"
 verbose="true"
 localTrusted="true"
 timeout="60000"/>
 
 <junitreport todir="${reports.xml}">
 <fileset dir="${reports.xml}">
 <include name="TEST-*.xml" />
 </fileset>
 <report format="frames" todir="${reports.html}" />
 </junitreport>
 </sequential>
 </target>
</project>
The output is:
Buildfile: C:\EclipseWorkspace\tests\Source\Flex\build_test.xml
test-init:
run-flex-tests:
[flexunit] Validating task attributes ...
BUILD FAILED
C:\EclipseWorkspace\tests\Source\Flex\build_test.xml:23: java.lang.NullPointerException
Total time: 297 milliseconds
Is there something obvious I am missing?
Thanks for any help!
Trevor

Brian,
OK, a colleague worked with me (thanks, John!) to debug the problem a little further, and I think we found the fundamental problem. I wanted to post that info to save you some time...
Aside: One thing we did have to do was to rebuild the flexUnitTasks.jar to include debug information, since the binary in the 4.1 beta 2 package did not have debug=true. I'd suggest that we might want to change the build script to build the binaries with debug moving forward.
Back to the problem.
The NullPointerException is thrown in TaskConfiguration::validateSharedProperties(), when equals() is invoked. Here is the code snippet:
 //if we can't find the FLEX_HOME and we're using ADL or compilation
 if((flexHome == null || !flexHome.exists()) && (testRunConfiguration.getPlayer().equals("air") || shouldCompile()))
 throw new BuildException("Please specify, or verify the location for, the FLEX_HOME property. "
 + "It is required when testing with 'air' as the player or when using the 'testSource' element. "
 + "It should point to the installation directory for a Flex SDK.");
In my case, I do not have a FLEX_HOME property set in Ant currently. I'll bet most folks have this set, so the logic would run differently for them. For my case, the (flexHome == null) check is true. That means that the testRunConfiguration.getPlayer().equals("air")check will occur next, and here is the problem. The "player" member is not set in the testRunConfiguration yet at this point, so testRunConfiguration.getPlayer() returns null. testRunConfiguration.setPlayer() is called in generateDefaults(). But generateDefaults() is not called until after validateSharedProperties() is called. So, if properties initialization could be improved here and I think this code will run more robustly.
I can work-around my issue temporarily by just setting a FLEX_HOME property in Ant. But I hope you will agree that the initialization issue with "player" still should be addressed. Would you like me to open a bug report, or is this thread enough?
Thanks,
Trevor

Flexunit ant task on CI Server - rundll32.exe causing problems

My team is using flexunit and a CI server running Hudson. On a development system, everything runs fine, and we get the reports just like we need them. It also works fine on the CI server when just the flexunit task is run, but the build fails when the CI server tries to run a full build - the build tries to run the tests and clean to prepare for the next build, but the clean fails because there is a "rundll32.exe" process using one of the files and it can't be deleted. We tracked this process down to the one run by the flexunit task.
Our task is:
 <target name="xci-test" depends="set-flex-coverage-home, prepare-domain-metadata-to-war, prepare-sounds-to-war, prepare-domain-metadata-for-testing, compile-unit-test-flex">
 <echo>**** The flexunit target requires that you have the standalone flash player installed and configured to run .swf files automatically! ****</echo>
 <mkdir dir="${dir.flexgui.test.output}"/>
 
 
 <flexunit workingDir="${dir.flexgui.test.output}"
 swf="${dir.flexgui.build.war}/${flex.swf.name}test.swf"
 toDir="${dir.flexgui.test.output}"
 haltonfailure="false" verbose="true" localTrusted="true"
 port="11028" timeout="40000"/>
 
 <junitreport todir="${dir.flexgui.test.output}">
 <fileset dir="${dir.flexgui.test.output}">
 <include name="TEST-*.xml"/>
 </fileset>
 <report format="frames" todir="${dir.flexgui.test.output}/"/>
 </junitreport>
 <sleep seconds="10"/>
 </target>
I can reproduce this behavior on my dev machine by running "ant xci-test clean". We tried putting a sleep in to give the process time to shut down, no change. We attempted to use the 'command' option to the flexunit task to bypass the use of rundll32.exe, but then the flash player just hangs onto the file and the clean still fails. Since "ant xci-test" followed by "ant clean" works, we also tried running ant from within ant in order to force the process to stop, but that also didn't work. Any help on this would be greatly appreciated.
Thanks for your time,
Linden

@Linden - Have not heard of this side effect from anyone as of yet, but good to know. Sounds like the file lock is coming from the Flash Player and causing the spawning process (rundll32.exe) to hang around as well. The FlexUnit team runs on Hudson using the FlexUnit Ant task, but we don't seem to encounter the same issue. What's the longest interval you've tried to use with the sleep task? Does the FP ever release its handle to the test SWF on your development machines?
Not sure this is a problem with the FlexUnit Ant task, but in 4.2 we could try to explicitly kill the rundll32 process since we'll have the PID when the task launches it. Head on over to JIRA and file a feature request for us and I'll see what I can do in the new year. In the short term though, maybe try upgrading your version of the stand alone debug flash player to see if that helps. Has anyone else seen this issue? Could you possible just move the clean target to be called before the xci-test target is run? Just some suggestions.
-Brian

Eclipse and WebLogic Ant Tasks

In WL_HOME/server/lib/ant/ is an ant.jar. It has a "defaults.properties" containing all of the ant taskdefs. I tried to extract that so that my build.xml could use them but it keeps complaining about weblogic.ant.taskdefs.perforce.P4Changes cannot be found. The reason why is that it's under the wrong package. How does one run the weblogic ant tasks outside of the weblogic ant installation? Thanks, Jeremy

bengali.Hi,
you also have to include a <taskdef> for the servicegen task of >weblogicThat's why I did but I still have a problem with the source2wsdd
ant task ( the other tasks run correctly within Eclipse).
I get a :
[source2wsdd] source2wsdd: Cannot find doclet class weblogic.webservice.tools.ddgen.ServiceGen
[source2wsdd] 1 error
BUILD FAILED: build.xml:324: javadoc execution failed
Total time: 3 seconds
The problem is that my source2wsdd has been defined with a well suited classpath
and is also called with the right classpath.
The problem only happens with this task !
Bengali

Built-in wlst ant task does not work in weblogic 10.3.1

Hi,
We have an installer script that deploys an ear file to a weblogic managed server. The script also invokes the build-tin wlst ant task to bounce the managed server. However, in version 10.3.1 the wlst task seems to be broken. I get this error:
[echo] [wlst] sys-package-mgr: can't create package cache dir, '/u00/webadmin/product/10.3.1/WLS/wlserver_10.3/server/lib/weblogic.jar/./java
tmp/wlstTemp/packages'
[echo] [wlst] java.io.IOException: No such file or directory
[echo] [wlst] at java.io.UnixFileSystem.createFileExclusively(Native Method)
[echo] [wlst] at java.io.File.checkAndCreate(File.java:1704)
[echo] [wlst] at java.io.File.createTempFile(File.java:1792)
[echo] [wlst] at java.io.File.createTempFile(File.java:1828)
[echo] [wlst] at com.bea.plateng.domain.script.jython.WLST_offline.getWLSTOfflineInitFilePath(WLST_offline.java:240)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[echo] [wlst] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[echo] [wlst] at java.lang.reflect.Method.invoke(Method.java:597)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.getOfflineWLSTScriptPath(WLSTUtil.java:63)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.setupOffline(WLSTUtil.java:214)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:133)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:75)
[echo] [wlst] at weblogic.ant.taskdefs.management.WLSTTask.execute(WLSTTask.java:103)
[echo] [wlst] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
Obviously that is not a valid directory...so I am wondering what it is trying to do, and why. The wlst task worked perfectly in 10.3.0. No changes were made when attempting to run the script against 10.3.0 and 10.3.1, which tells me that something is different with the 10.3.1 setup. Here is the ant code I am running:
<target name="init-taskdefs">
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="ant-ext/ant-contrib.jar" />
</classpath>
</taskdef>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" />
<taskdef name="wlst" classname="weblogic.ant.taskdefs.management.WLSTTask" />
</target>
<macrodef name="wlShutdownServer">
<attribute name="adminUser" default="${deploy.admin.username}" />
<attribute name="adminPassword" default="${deploy.admin.password}" />
<attribute name="adminUrl" default="${deploy.admin.url}" />
<attribute name="serverTarget" />
<sequential>
<trycatch property="server.error">
<try>
<wlst failonerror="true"
arguments="@{adminUser} @{adminPassword} @{adminUrl} @{serverTarget}">
<script>
adminUser=sys.argv[0]
adminPassword=sys.argv[1]
adminUrl=sys.argv[2]
serverTarget=sys.argv[3]
connect(adminUser,adminPassword,adminUrl)
target=getMBean("/Servers/"+serverTarget)
if target == None:
target=getMBean("/Clusters/"+serverTarget)
type="Cluster"
else:
type="Server"
print 'Shutting down '+serverTarget+'...'
shutdown(serverTarget,type,'true',15,force='true')
print serverTarget+' was shut down successfully.'
</script>
</wlst>

<echo message="Deleting any lok files that have not been removed..." />
<delete failonerror="false">
<fileset dir="${env.DOMAIN_HOME}/servers/@{serverTarget}" includes="**/*.lok"/>
</delete>
</try>
<catch>
<fail message="@{serverTarget} shutdown failed. ${server.error}" />
</catch>
<finally/>
</trycatch>
</sequential>
</macrodef>
Any help would be appreciated. Thanks!

Well, it looks like passing something like "-Djava.io.tmpdir=/var/tmp/javatmp/`date +%Y%m%d`" to ant did the trick. I had to make sure that directory existed first, otherwise it threw a java ioexception.
I still don't understand what changes between 10.3.0 and 10.3.1 to necessitate this change.

Unable to run ALBPM Ant tasks on Linux

Hi,
I am trying to execute a simple build script that creates a session with given directory details and deploys/publishes a project on to the Enterprise Server. With usual modifications, this scripts works fine on Windows, but on Linux it keeps on giving an error that makes no sense. I am copying my build file as well as error stack trace below. Please help me on urgent basis.
OS: Linux 64 bit
Oracle Enterprise Server: 10.3.1.0.0
JAVA_HOME=/usr/java/jdk1.6.0_16
ANT_HOME=/usr/ant/apache-ant-1.8.1
build.xml

<project name="sampleproj"
 xmlns:fuego="antlib:fuego.tools.ant.enterprise"
 xmlns:fuego.j2ee="antlib:fuego.tools.ant.j2ee">

<property file="build.properties"/>
<echo message="Enterprise Home Directory:: ${fuego.basedir}" />
<echo message="Ant Version:: ${ant.version}" />
<echo message="Connecting to directory:: ${fuego.directoryid}" />
<fuego:passport id="passport"
directoryid="${fuego.directoryid}"
preset="engine" />
<target name="publish-on-linux" description="Publish and deploy processes">
<echo message="Creating session..."/>

<fuego:session passportref="passport"
verbose="true"
haltonerror="true">

<fuego:publish fpr="${bpm.project.path}"
deploy="true"
engine="${fuego.engine}"
 haltonerror="true"
 importdata="true"
 automapconfigs="true"
 automapvars="true"
 automaproles="true"
 automapbuspars="true"
 importcustomviews="true">
</fuego:publish>
</fuego:session>
</target>
</project>
build.properties
# Enterprise installation directory
fuego.basedir=/opt/OraBPMwlHome
# Name of ALBPM Engine to deploy to
fuego.engine=bpmengine
# Project to deploy
bpm.project.path=/usr/test_ant/sampleproj
# Directory details
fuego.directoryid=default
Error on running the target publish-on-linux
[echo] Enterprise Home Directory:: /opt/OraBPMwlHome
[echo] Ant Version:: Apache Ant version 1.8.1 compiled on April 30 2010
[echo] Connecting to directory:: default
publish-on-linux:
[echo] Creating session...
[fuego:session] fuego base dir [opt/OraBPMwlHome]
BUILD FAILED
/usr/test_ant/build1.xml:25: java.lang.NullPointerException
at fuego.tools.ant.BaseFuegoTask.getClassLoader(Unknown Source)
at fuego.tools.ant.BaseFuegoTask.executeTask(Unknown Source)
at fuego.tools.ant.enterprise.taskdefs.DirectorySessionTask.executeImpl(Unknown Source)
at fuego.tools.ant.BaseFuegoTask.execute(Unknown Source)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
at org.apache.tools.ant.Main.runBuild(Main.java:801)
at org.apache.tools.ant.Main.startAnt(Main.java:218)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 0 seconds

Amit Zini wrote:
Dear All,
I am unable to run my oracle 10g forms application on Linux machine which is runing Fedora 16.
i have tried to install jre 6 but mozilla firefox 10 is not loading my oracle 10 forms application, it says plugin missing.
Kindly help me to short out the problem.
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.1) (fedora-65.1.11.1.fc16-i386)
OpenJDK Server VM (build 20.0-b12, mixed mode)
Regards.
Amit.Try with down grade of Mozilla firefox. may be version 6 to 8. not 9/10.
Firefox with 9 and higher doesn't support JRE version 1.6.XX.
Hopes this helps

Deploying bpm 11g project sar file using ant task

I am trying to deploy the bpm project using ant task file. The status I get is [deployComposite] ---->Deploying composite success. However when I check the deployments, they are not there. If I try to deploy this using Jdeveloper it works correctly. I need to get this to work for production deployments. Any suggestions?
C:\Oracle\Middleware\Oracle_SOA1\bin>ant -f ant-sca-deploy.xml -DserverURL=http:
//10.140.183.71:7001 -DsarLocation=N:\RuleBasedProjectInitiate\deploy\RequestPro
ject.ear -Doverwrite=true -Duser=weblogic
Buildfile: C:\Oracle\Middleware\Oracle_SOA1\bin\ant-sca-deploy.xml
[echo] oracle.home = C:\Oracle\Middleware\Oracle_SOA1\bin/..
deploy:
[input] skipping input as property serverURL has already been set.
[input] skipping input as property sarLocation has already been set.
[deployComposite] created temp dir =C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cli
ent_1279894885343
[deployComposite] Creating HTTP connection to host:10.140.183.71, port:7001
[deployComposite] Enter username and password for realm 'default' on host 10.140
.183.71:7001
[deployComposite] Authentication Scheme: Basic
[deployComposite] Username:
weblogic
[deployComposite] Password:
[deployComposite] Received HTTP response from the server, response code=200
[deployComposite] clean up temp dir: C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cl
ient_1279894885343
[deployComposite] ---->Deploying composite success.
BUILD SUCCESSFUL
Total time: 4 seconds
C:\Oracle\Middleware\Oracle_SOA1\bin>

You can always deploy the ADF web apps from the Application (top menu) deploy option. Just make sure you're deploying the EAR profile for the project. Deploying the web projects from the composite deployment wizard can be convenient. But I think it's often the case that you deploy them (the composite and forms) separately (e.g. you make a series of changes to the composite without needed to redeploy the UI projects).
Bottom line is you don't have to delete the projects to be able to modify/deploy them.

Ant task cyclic library refrence

Hello everyone,
I am using flex ant task from my Flash builder to compile application. Its working fine and I am able to get the output. But the problem is whenever I use a library in my main project which is refrencing other library than I am unable to find refrence of components in lib 2. Below is the structure
NewLib >> contains a NewLibGrid(which is a normal spark grid)
MainLib >> ExtPanel which includes NewLibGrid from NewLib .
MainApp >> This uses ExtPanel
No I am getting error during ant compilation
[compc] D:\Data\Flex\Projects\CompLib\src\ExtPanel.mxml: Error: Could not resolve <local:NewLibGrid> to a component implementation.
Here is part of antscript I am using
<target name="lib1" depends="lib2">
<compc output="${STAGE_DIR}/stagingDir/CompLib.swc"
 keep-generated-actionscript="${DEBUG}"
 debug="${DEBUG}"
 optimize="${OPTIMIZE}"
 target-player="${TARGET_FLASH_PLAYER}"
 include-classes="ExtPanel">
<runtime-shared-library-path path-element="${FLEX_HOME}/frameworks/libs/framework.swc">
<url rsl-url="framework_${FLEX_VERSION}.swf"/>
<url rsl-url="framework_${FLEX_VERSION}.swz"/>
</runtime-shared-library-path>
<runtime-shared-library-path path-element="${PROJ_HOME}/NewLib/bin/NewLib.swc">
<url rsl-url="${PROJ_HOME}/NewLib/bin/NewLib.swf"/>
<url rsl-url="${PROJ_HOME}/NewLib/bin/NewLib.swz"/>
</runtime-shared-library-path>
<compiler.library-path dir=".." append="true">
<include name="Common/libraries"/>
<exclude name="global_library.swc" />
</compiler.library-path>
<source-path path-element="../CompLib/src" />
</compc>
</target>
<target name="lib2">
<compc output="${STAGE_DIR}/stagingDir/NewLib.swc"
 keep-generated-actionscript="${DEBUG}"
 debug="${DEBUG}"
 optimize="${OPTIMIZE}"
 target-player="${TARGET_FLASH_PLAYER}"
 include-classes="NewLibGrid">
<runtime-shared-library-path path-element="${FLEX_HOME}/frameworks/libs/framework.swc">
<url rsl-url="framework_${FLEX_VERSION}.swf"/>
<url rsl-url="framework_${FLEX_VERSION}.swz"/>
</runtime-shared-library-path>
<compiler.library-path dir=".." append="true">
<include name="Common/libraries"/>
<exclude name="global_library.swc" />
</compiler.library-path>
<source-path path-element="../NewLib/src" />
</compc>
</target>

 <mxmlc
 file="${project.name}/src/Test.mxml"
 output="${build.mxmlc.dir}/Test.swf"
 static-link-runtime-shared-libraries="true"
 >
 <load-config filename="${air.config}"/>
 <source-path path-element="${project.name}/src" />
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/framework.swc">
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swz"/>
 <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/datavisualization.swc">
 <url rsl-url="${rsl.dir}/datavisualization_3.2.0.3958.swf"/>
 </runtime-shared-library-path>
 </mxmlc>
This also seems to work. AIR libraries are included in my output SWF. It all happens right when I have static-link-runtime-shared-libraries="true" . Why? Why does that not work when i have static-link-runtime-shared-libraries="false" ??

Ant task to include Halo theme

Similar Messages

Maybe you are looking for