A Look at Flex 3.0's Java-based Compiler API
Integrating Java and Flex has proven challenging in some cases. Adobe is trying to make things easier with its release of Flex 3 which includes a Java-based compiler API. This API lets you compile SWF and SWC files from Java applications, supporting the same options as mxmlc and compc command-line tools.
The underlying concept relies on Java developers creating Flex Application objects. These objects represent a Flex application, and are built by and setting its mxml as well as its output and building it:
Application application = new Application(new File("../apps/TestApp.mxml"));
long result = application.build(true);
Some of the highlights of the Flex Java API are:
Generate reports and provide information such as progress and logs during the compilation process as well as reports about the application, library, or project that you are compiling
Incremental compilation that is more efficient because it only recompiles the virtual file that was changed and not all files that are in the application
The capability to create application and library source files at run time and to compile these files into applications and libraries.
Create Flex applications in memory and compile them to SWF files without ever having an MXML file on disk.
There are already some tools that can help out Java developers wanting to build Flex applications. Antennae, a set of templates for building complex Flex projects with Ant has been available for some time now. Also based in mxmlc and compc, Antenne gives developers another means for intergrating Flex into their Java projects.
The Flex 3 Java-based compiler API can be found here.
What is the big deal
Yes having the linkage reports would be nice too.
Re: 3 news
Re: 3 news
a) non-free Flex plugin for eclipse (299 USD without charting and 699 USD with Charting component, given the fact that a lot of very good eclipse plugins are available for free or are are available for under 50 bucks (like MyEclipseIDE))
b) having to buy FDS (flex data services) license for deploying it as an integration bit to any J2EE appserver deployment.Although there are other alternatives available but they don't perform as well.
Quoting Yakov Fain (well known Flex Evangelist) from his article(flexblog.faratasystems.com/?p=163)
While you can use Flex just to connect to your existing applications written as JSP or any other HTTP-compatible technologies, you’ll get performance gain if you’ll use Flex remoting and messaging that is build on fast Adobe proprietary protocols called AMF3 and Real Time Messaging Protocol (RTMP). To take advantage of these benefits you have to purchase Flex Data Services licenses, while may not be affordable for small businesses.
I think once these bounds are removed, Flex's adoption in the Java Enterprise world will increase rapidly as a strong RIA alternative. Just my 2 cents.
Re: 3 news
I would mention that I did read this article. But my point is, Flex can become
more attractive to small java shops (like mine) if its pricing (*with charting and FDS license(100 concurrent users)) comes down to around 100 USD.
I am a Flex fan (*from the looks of it) but would like the pricing to be adjusted a bit more before using/promoting it in my network.. I hope ADOBE product management is reading ;-)
good news (Free alternative for Flex Builder is in the making..)
Also a free alternative to Flex Data Services - GDS (Granite Data Services) is also been announced here on infoq. Its available @ www.graniteds.org/confluence/pages/viewpage.act...
Good stuff going on in the Flex/RIA market. I am excited to see how things unfold in the near future... who knows if Adobe notices there are competitive (FREE) alternatives popping up to Flex builder, they might make it free (or at least cheaper ... :-)
Re: good news (Free alternative for Flex Builder is in the making..)