<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>success</status>
  <result>
    <project>
      <id>56297</id>
      <name>jsf-flex</name>
      <created_at>2008-12-17T07:46:39Z</created_at>
      <updated_at>2009-12-28T09:37:12Z</updated_at>
      <description>Abstract 

JSF Flex goal is to provide users capability in creating standard Flex components as JSF components {note dynamic charts and some other components are not part of standard Flex components}. So users would create the components as normal JSF components and the project will create the necessary MXML, SWC, SWF files and etcetera and link the values of the components back to the managed beans using JSON+Javascript and Actionscript. {standard Flex components have been open sourced through MPL license}. Also MXML_BASIC renderKitId allows utilizing other renderKits within the same view {i.e. HTML_BASIC}, allowing mix of JSF Flex components and other components such as standard HTML components. If you are curious of how the code is implemented, you can check out the following Wiki page which contains a brief overview : JSFFlexProcess. There exists various configuration fields that can be set within web.xml, but one noteworthy field is com.googlecode.jsfFlex.MODE which must be set to productionMode after creating SWF, SWC, and etcetera files in debugMode. 

Following is a Wiki page containing info of JSF Flex project's Maven repo which has been created on April 18th, 2009 : JsfFlexMavenRepo. 

The project aim is to support the following JSF implementations {bold faced are currently supported} : 

MyFaces  1.2  2.0 Mojarra  1.2  2.0 

Quick Start 

Following Wiki page contains info in importing the example WAR file and adding the project's Jar artifacts to a new Dynamic Web Project =&gt; QuickStart. 

Since following information is so critical, it is being duplicated within the home page. When one is finished tweaking of creating the components/tags, one MUST change the com.googlecode.jsfFlex.MODE field within web.xml to productionMode to avoid the cost of creating preMxml, Mxml, Swf, and etceteras. Also one should copy all the system generated directories under Webcontent/swf/* to their corresponding directory within the Workspace during the move to higher env {since the system uses servContext.getRealPath(&quot;&quot;) as the root directory of preMxml, MXML, and SWF directory and} 

Tomcat on default for example flushes it out to their cache directory under metadata i.e. C:\OpenSource\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\jsf-flex-examples JBoss on default for example flushes it out to their temp directory i.e. C:\Program Files\jboss-4.2.3.GA\server\default\tmp\deploy\tmp46689jsf-flex-examples.war  

Release Info 

Recent changes for current Download artifact 1.0.1 BETA are : 

This release has been made, so that focus can be spent on JSF 2.0 integration {which will provide easier + more friendly asynchronous communication} Change from usage of Qdox Javadoc to Annotation Code written in JDK 5.0 Support of Flex version 3.4 {i.e. DateChooser component and locale support according to the change needed of copyLocale execution for Flex version 3.x} Capability to submit the form data using mxmlButton or mxmlLinkButton tags Tweaking of performance { usage of Executors in some of the tasks to possibly assist in creation of multiple SWF + locale; however swc + swf creation is dependent upon Flex SDK } Capability in creating components outside of JSF Flex by providing the component name + attributes as tag attributes One thing to note is the size of the download artifacts. Since Flex SDK now comes packaged with Air tools to allow creation of Air applications for Flex components, the size of flexSDK has been increased rather largely {that's the reason the first hit to any .xhtml or .jsf page will take a bit of time, but afterward the time should be relatively similar when hitting additional pages to create SWF, SWC, and etcetera within debugMode. please note that when one is done, one should change the configuration to productionMode to see it's actual performance}. There exists two reasons of why Air library hasn't been ripped out of flexSDK that is downloaded with the Jars :  First is for safety, meaning it is better to leave them in then to find out later that one needs certain Jars that has been removed Second is a possible investigation of creation of Air. Strong emphasis on possible. 

For the next major Beta artifact 1.1 BETA release there will be support for : 

Support of JSF 2.0 Support of latest,stable Flex version Capability of using MethodExpression for additional components. Additional functionality such as the current DataGrid component where there will be further interweaving of JSF/Java + ActionScript content.  Fixes found in additional testing. Clean up of code and additional functionality when thought of. 

There exists a screen shot of an example .jsf at the bottom of this page and below are URLs for the latest SNAPSHOT Downloads : 

View HandlerMojarra URLMyfaces URL JSPhttp://localhost:8080/jsf-flex-examples-mojarra12Impl-1.0.1b/mxmlIndex.jsfhttp://localhost:8080/jsf-flex-examples-myfaces12Impl-1.0.1b/mxmlIndex.jsf Facelet using XHTMLhttp://localhost:8080/jsf-flex-examples-mojarra12Impl-1.0.1b/faces/mxmlIndex.xhtmlhttp://localhost:8080/jsf-flex-examples-myfaces12Impl-1.0.1b/faces/mxmlIndex.xhtml 

Testing Performed 

Brief testing has been performed using Sun's JVM as JAVA_HOME : 



Operating System  Browser Tested                  Servlet Container/Application Server Tested  Windows XP          Firefox 2.0 , IE 6.0, Opera 9.25  TomCat 6.0, JBoss 4.2             Linux               TODO                              TODO                         Mac                 TODO                              TODO                        

Roadmap 

Please refer to the following wiki page for information regarding what is planed for support within release 1.0 BETA =&gt; RoadMap. 

Meritocracy 

The projects plans to do everything possible to encourage an environment that supports a meritocracy. Meaning any developer/member who has contributed dearly to the project and knows of the project's design will be promoted to an owner status. 

Rationale 

With the Web 2.0 technology flourishing within the web world, this would be a great opportunity in creating a project and bridging technologies such as Adobe Flex with JSF. 

Specifically the project will provide : 

Easy creation of standard Flex applications while preserving the ease of databinding to legacy systems through JSF An alternative to purchasing Flexbuilder when creating simple Flex applications</description>
      <homepage_url>http://code.google.com/p/jsf-flex</homepage_url>
      <download_url></download_url>
      <url_name>jsf-flex</url_name>
      <user_count>0</user_count>
      <average_rating></average_rating>
      <rating_count>0</rating_count>
      <analysis_id></analysis_id>
      <licenses>
        <license>
          <name>apache_2</name>
          <nice_name>Apache License 2.0</nice_name>
        </license>
      </licenses>
    </project>
  </result>
</response>
