Communities

  Discussions Documents Blog Posts
OpenFaces Components 190    
Validation Framework 2    
General Feedback 25    
Ajax Framework 10    
Migrating from QuipuKit 1.x 2    

Latest Poll

Are you going to use JSP with JSF 2.0?

Now that JSF 2.0 has standardized Facelets as a default view declaration language, and deprecated JSP, would you anticipate OpenFaces 3.x continue support of JSP? Feel free to share your considerations in comments.

Yes, we'll have to use JSF 2.0 with JSP. (23%) No, let's move on to the new standard! (46%) Not sure -- I'll just use JSF 1.2 for a while. (31%) Total Votes: 13 - Full Results

Recent Blog Posts

We're pleased to present the second Early Access release for OpenFaces 3.0 with JSF 2.0 support. This release features tighter integration with the JSF 2.0 infrastructure, which has resolved most of the problems that existed in the previous release. Here are the most notable fixes:

  • fixed Ajax functionality for DataTable, TreeTable, CompositeFilter and all other components;
  • fixed compatibility with the standard JSF 2.0 Ajax APIs (the <f:ajax> component, and jsf.ajax.request() JavaScript function);
  • made possible to attach client behavior tags, such as <f:ajax> to all OpenFaces input and command components

 

Besides, it is now easier to add OpenFaces to your application -- you just need to add OpenFaces jar with its dependencies to your application. No web.xml modification and resource filter registration is required anymore!

 

You can download this version and the demo package that runs on Tomcat and GlassFish v3 here (see the OpenFaces 3.0 Early Access 2 section). If you've used the previous release, please also read the migration instructions in the release notes document.

 

This is the last milestone before the final release of OpenFaces 3.0. We'd like to have your feedback on how it behaves in your JSF 2.0 applications in order to polish the library by the actual release. Please post your feedback and share your experience on the product's forum.

2 Comments Permalink

Here are the changes that were made since the previous early access milestone.

Improvements

  • It's now easier to add OpenFaces to your application: you just need to add OpenFaces jar and its dependencies. No web.xml modification and resource filter registration is required anymore. See the "Installation and Configuration" section in developer's guide for details.

Resolved Issues

  • Fixed Ajax functionality for DataTable, TreeTable, CompositeFilter and all other components.
  • Fixed compatibility with the standard JSF 2.0 Ajax APIs (the <f:ajax> component, and jsf.ajax.request() JavaScript function).
  • Made possible to attach client behavior tags, such as <f:ajax> to all OpenFaces input and command components.

Known issues

  • Session expiration notification for Ajax calls doesn't work currently.

 

Migration Instructions

  1. OpenFaces requires the latest version of Mojarra, 2.0.3, since it has some fixes critical for proper functionality of OpenFaces components. You can download Mojarra 2.0.3 here. If you're running your application on Glassfish application server, make sure to update Mojarra in Glassfish (see the instructions).
  2. Remove ResourceFilter declaration and mapping from application's web.xml.
  3. Make sure to use <h:head> and <h:body> tags instead of old-style plain <head> and <body> tags.

 

Note: running OpenFaces demo, which is available for download, on Glassfish application server, requires the latest version of Mojarra (Mojarra 2.0.3) to be installed in the Glassfish server. See the installation instructions.

0 Comments Permalink

We're glad to announce the first early access milestone of the new OpenFaces 3.0 version featuring JSF 2.0 compatibility. Now developers creating JSF 2.0 based applications have access to rich possibilities provided by all kinds of OpenFaces components, ranging from DataTable and TreeTable for flexible data display, to BorderLayoutPanel and Window for creating various layouts, and Validation framework for client-side validation and additional validators.

 

OpenFaces 3.0 will be maintained in parallel with OpenFaces 2.0 and both of them will have the same set of features, but they will target different versions of JSF: 2.0 and 1.2 respectively. The final release for the OpenFaces 3.0 version is expected in June.

 

You can download the new version and the demo package that runs on Tomcat and GlassFish v3 here (see the OpenFaces 3.0 Early Access 1 section).

 

As JSF 2.0 support is currently on an intermediate stage, some functionality is limited yet and there are the following known issues in OpenFaces 3.0 EA1:

- State saving during OpenFaces Ajax requests has some issues when using the built-in Ajax capabilities in certain OpenFaces components. Most notable consequences are: a) impossibility to use Ajax node folding in TreeTable, so only client-side node folding works fine yet, and b) DataTable paginator's "next" button which can't be used more than once.

- The CompositeFilter component doesn't work in this Early Access version.

 

Feel free to share your feedback and ask any questions on the product's forum. Stay up to date with the latest OpenFaces news by following us on Twitter.

8 Comments Permalink


We're introducing the new OpenFaces LevelIndicator component which is already available in the latest nightly builds.level-indicator-default-vertical.png

LevelIndicator  - a component that shows a numeric value in graphic style, similar to the LED volume meter and resource meter used in Windows Task Manager.

 

LevelIndicator component can be defined on the page using <o:levelIndicator> tag. LevelIndicator can be provided with the level value that it will represent. The value should be of typejava.lang.Double and be in [0..1] range.

 

On the following examples you can see the LevelIndicator component in it's default horizontal and vertical states.

level-indicator-default-horizontal.png

 

The component has transitionLevels and colors attributes, so using these attributes you can define value ranges and specify appropriate colors for them.

 

<o:levelIndicator value="0.8" colors="blue,orange,violet" transitionLevels="0.35, 0.6" />

 

The upper declaration defines that LevelIndicator component has two transition level points at 0.35 and 0.6,

this means that LevelIndicator has three value ranges([0 - 0.35] , [0.35 - 0.6] , [0.6 - 1]).

 

Each of defined value ranges will use each own color, defined in colors attribute of <o:levelIndicator> tag. The result component's representation can be seen on the example below.

level-indicator-with-custom-colors.png

As it can be seen from the example below, the component's styles and sizes can be easily customized to the desired look.

  <o:levelIndicator value="0.8"
                    style="background-color: #e6e6e6; border: 1px solid #333; width: 350px; height: 40px;"
                    segmentSize="5"
                    colors="blue,orange,violet"
                    transitionLevels="0.35, 0.6"/>

level-indicator-with-custom-css.png

0 Comments Permalink

We're glad to announce a preview of the JSF 2.0 compliant version of OpenFaces. This is not yet the 3.0 EAP1 milestone mentioned in our Roadmap, which will be published soon but you can already check out OpenFaces in a JSF 2.0 environment and give us some valuable feedback before the upcoming EAP1 version.

 

Here are the OpenFaces 3.0 Preview download files:

openfaces-3.0.preview1.zip -- contains the new openfaces.jar file and runtime dependency jar files.

openfaces-3.0.preview1-src.zip -- source code for the new version.

openfaces-3.0.preview1-demo.zip -- contains the demo application war file deployable under GlassFish v3 and Tomcat 6.x.

openfaces-3.0.preview1-demo-src.zip -- demo source code.

 

The installation instructions are the same as for OpenFaces 2.0 for now, see the documentation. Please note also that OpenFaces versions 2.0 and 3.0 are going to have the same features but run under different versions of JSF -- 1.2 and 2.0 respectively.

 

The JSF 2.0 compatibility support is on an intermediate stage yet though most of the components are already functional. Here are the known issues in this version:

- State saving during OpenFaces Ajax requests has some problems, which results in some issues with built-in Ajax capabilities in certain OpenFaces components. For example DataTable paginator's "next" button can't be used twice and there are certain problems when using the Ajax node folding in TreeTable (hwever client-side TreeTable node folding with preloadedNodes="all" works fine now).

- The CompositeFilter component doesn't work in this version.

- There are numerous validation messages at the bottom of each demo page, though these messages don't affect the demo application's functionality.

- The documentation is not updated to reflect the JSF 2.0 related specifics yet.

 

Please share your feedback and any issues that you might have on the forum.

0 Comments Permalink

Recent Content

Subject Author
Re: Some not-wanted TextArea rendered when use DataTable or DateChooser components 9 hours ago by Dmitry Pikhulya Dmitry Pikhulya
Re: JSF 2.0 - Openfaces 3.0 EA2 11 hours ago by Dmitry Pikhulya Dmitry Pikhulya
Re: Error openfaces-2.x-nightly-build 1 day ago by Dmitry Pikhulya Dmitry Pikhulya
Open Faces and view PDFs 2 days ago by Juanca Juanca
Re: Openfaces <o:window> 1 week ago by Natalia Zolochevska Natalia Zolochevska
Re: Help windows 1 week ago by Natalia Zolochevska Natalia Zolochevska
o:window is not working in IE6 with nightly build 2 weeks ago by rajasekhar rajasekhar
Nodeselection on rerendered Treetable not working as expected 3 weeks ago by Smitha Smitha
Re: OpenFaces with facelets in Eclipse Helios 3 weeks ago by Shony Shony
What's New in Nightly Builds 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
Roadmap 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
OpenFaces 3.0 Early Access 2 with JSF 2.0 support 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
OpenFaces 3.0 EA2 Release Notes 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
Migrating from QuipuKit 1.6.2 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
Re: Is it possible to store a tree table's expansion so it can be reloaded? 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
Re: CommandButtons associated with Tree Table cells 1 month ago by Tod Tod
Re: Seam and OpenFaces - which scope should be used for binding? 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
Re: seam 2.z + richfaces 3.x + openfaces 1 month ago by Maynard Maynard
Re: Datatable single or multiple selection depending on some bean property? 1 month ago by Aysegul Aydın Aysegul Aydın
Re: dataTable and composite component 1 month ago by Sergey Sergey
Re: Make SortAscending and SortDescending menu items invisible in ColumnMenu if the column is not sortable 1 month ago by Aysegul Aydın Aysegul Aydın
Re: Filter Operations for Text Filter Type 1 month ago by Aysegul Aydın Aysegul Aydın
Re: Is draggable working for o:window? 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
Re: OpenFaces with JSF 2.0 1 month ago by Dmitry Pikhulya Dmitry Pikhulya
Re: Resource Serving Problem when Refreshing with OpenFaces 3.0EA1 2 months ago by Dmitry Pikhulya Dmitry Pikhulya