I'm a JBoss core developer at Red Hat, and the AeroGear project lead. I previously lead the RichFaces project, and have been involved in many other open source projects such as Seam, and JBoss AS. I'm passionate about promoting open source, community, and standards. I server as a W3C representative for Red Hat, and have been part of multiple Java Community Process (JCP) specifications, currently on the JSON API expert group. I have been architecting and developing enterprise applications and projects for over fourteen years, specializing in mobile device integration, web tier frameworks, UI design, and integration.
Several of us from JBoss will be presenting at JSFSummit in Orlando Florida between December 1st and 4th. We'll be covering lots of different content from general RichFaces
how-to sessions, advanced component demos, JSFUnit, Seam, CDI, and other JSF related topics.
- RichFaces Component Toolbox: Today and Tomorrow by Jay Balunas
- The Best Kept Secrets of Seam, RichFaces, JSF and Facelets by Jay Balunas
- CDI (JSR-299), Weld and the future of Seam by Dan Allen
- JSF 2: Keeping Progress Coming by Dan Allen and Andy Schwartz
- Seam & RESTeasy: You haven't seen REST yet by Dan Allen and Lincoln Baxter III
- Maturing your application's security with Seam Security by Dan Allen
- Dumping JSF by Stan Silvert
- Holistic testing of JSF applications by Stan Silvert
Also don't forget to register if you have not already!!
Nick Belaevski is the RichFaces dev lead in Minsk and has officially joined the JSF 2.0 Expert Group (JSR-314) along with Alex Smirnov to represent RichFaces and Exadel. As many of you know Dan Allen and Pete Muir are also on the JSF 2.0 Expert Group representing Red Hat & JBoss. Together these 4 people along with the rest of the EG will continue to help advance JSF as a standard and a technology.
Anyone who has worked with RichFaces at all is likely familiar with Nick (usually known as nbelaevski), either in the forums, Jira, or SVN. He has been an invaluable member of the RichFaces project for years, and brings a great level of insight into the EG.
Again, congratulations Nick!!
Unfortunately a few regression issues slipped through the cracks and were found by our community. To address these in a timely manor we have been working on, and just released 3.3.2.SR1 (Service Release). This release can be downloaded from our project's Stable Release page and accessed in maven using the version identifier 3.3.2.SR1 as usual.
There were only 6 jira issues resolved in the release and they can be reviewed here - 3.3.2.SR1 Jira page. Most have to do with the ExtendedDataTable, but others deal with Calendars, ModalPanel, and MenuItems.
Although we never like to have regressions slip through - I think that it is testament to the strength of our community that they were found so quickly and clearly reported. Thanks to all involved in this!!
Note: there were no changes to documentation so document links continue to point to 3.3.2.GA
Unfortunately a few regression issues slipped through the cracks and were found by our community (thanks). So in order to fix them we are going to be releasing 3.3.2.SP1 as soon as possible. For the list of jira's included in this very focused release please see the 3.3.2.SP1 Jira page. Sorry about this and we'll get this fixed and available ASAP. In the mean time please let us know of any other issues that you may find.
This is primarily a bug fix and stabilization release and you can review the 3.3.2.GA release notes and the 3.3.2.CR1 release notes for the complete list of issues addressed. For a listing of the most voted on issues you can check here ( voting for issues is a good way to get them attention ).
The whole team will now shift focus to the RichFaces 4.0 release with JSF 2.0 support. We are making good progress and would like to release an ALPHA2 version in a little over a month. As always please check out our weekly IRC meetings if you want the latest information or have topics to bring up. You can also subscribe to the RichFaces Twitter account to get important updates and links.
The next release of the 3.3.X branch will be 3.3.3.CR1 but we currently have no dates or plans for that. Obviously if there are any critical issues found in 3.3.2.GA or enough community contributions we'll revisit.
You can also check out my DZone interview on the RichFaces project for some more information on future plans, and RichFaces 4.0.
The RichFaces team is very happy to announce that the first ALPHA release of RichFaces 4.0.0 with JSF 2.0 support has been released. This first release will give all of you early adopters and fans out there a chance to play with the project. Any feedback, issues, comments, or patches are welcome as always.
You can download all the release artifacts at the RichFaces Download page and the readme.txt in the richfaces-4.0.0.ALPHA1 distribution contains all you need to get started and integrate the library into your application. You can also check out the Release Notes for even more details.
There are eight components completed for this first release. We will be adding more for each milestone including all the rich components.
- a4j:ajax (formally a4j:support)
Most function like their cousins in the 3.3.X series ( for now ), and the RichFaces demo application ( new name ideas welcome ) show them all.
We wanted a way for everyone to get started early with RichFaces 4.0 and try out the components so we created this component gallery example. The readme.txt file in the richfaces-examples-4.0.0.ALPHA1 download will have all the details, but here are steps to you started.
This demo application can be built and deployed to servlet containers and some JEE5 servers. For convenience we include 2 pre-built war files, one for each type of server. Note for testing we used both tomcat 6 and JBoss AS 5.1, and more will be added to this list.
You can also build the example fresh from the included source files. However note that we are currently building from the SNAPSHOT versions of the JSF 2 Mojarra project and this can sometimes cause issues. The build requires Maven 2.1.0 and can be built and ran 3 different ways:
Servlet container compatible war:
Then deploy to Tomcat 6.x or just run using maven and jetty with:
JEE5 compatible war:
mvn install -P jee5
Then deploy to JBoss AS 5.x/4.2.x or some other jee5 servers. Don't forget to update your server's JSF libraries to the latest snapshots of JSF 2.0 Mojarra project. For JBoss AS you can follow these directions: Upgrade JBoss AS to JSF2
Anyway you deploy the example you can access it with this link http://localhost:8080/richfaces-demo
Since we build using maven it is very easy to integrate with your favorite IDE. Use the standard maven commands for your IDE.
Then just import the project into your IDE and you can start playing!
This release also includes a preview of the 4.0 Component Development Kit (CDK). This will make creating rich JSF components a snap with helpful tools, maven archetypes, and more. Right now it is in a very early development state, and can be used to create very basic components. Follow these instructions for ALPHA1 CDK: RichFaces 4.0.0.ALPHA1 CDK Tutorial ( Watch this page for updates ).
We are planning another ALPHA release at the end of October, and regular BETAs to follow that. Each milestone will have more features and components. We will be discussing more details in the coming weeks and be updating both the wiki and jira to represent the changes - so keep an eye out if you are interested.
RichFaces is an open community project and we want to encourage anyone interested to get involved. That can be as simple as letting us know when you find a problem or answering questions on the forums, to submitting patches and helping to define direction and features.
We will be aiming for a 3.3.2.GA release at the end of September or early October.
The RichFaces team is proud to announce that the RichFaces project site has gotten a face lift!!
Check it out here http://www.jboss.org/richfaces
Some notable new pages:
- Community Page - information on how the community interacts
- Calendar Page - stay up to date on team meetings, talks, and releases
- Jira Page - details on entering jira's and RichFaces jira projects
- Source Code Page - get the details and dig into the source code here
- Demos Page - Links to our online demos
Don't forget to check out our wiki page for even more information and details.
Please let us know if you find any errors, or broken links to :-)
I have finally had the time to sit down and write up a summary of the RichFaces face-2-face meeting that took place a few weeks ago. I'll outline the major topics and some of the results that came out of it, as well as share some pictures from the meeting and the team event :-)
We met in Brno Czech Republic, which is a nice city and not too touristy. Red Hat has a large office in Brno for both Red Hat and JBoss activities. It was a nice middle ground to meet at and allowed us all to focus on nothing else but the meeting.
The 3.3.2 release is going to be a performance & bug fix release. We are planning on releasing the CR1 in late August and the GA sometime in September. Some of the highlights are:
- Remove internal CSS classes for performance optimizations RF-7215
- Optimize JavaScipt initialization RF-7246
- Example impovements Jiras
- Many others 3.3.2.CR1 Jiras
The 3.3.X branch will go into maintenance mode and will only have releases to cover critical issues, or if there are enough community contributions to warrant a release. This will allow the team to focus on the 4.0 release.
Much of what we discussed is already updated and in place in the RichFaces 4.0 Planning Wiki so I won't get into too many details here. The key areas with some links and info are below
Obviously the biggest update in 4.0 is complete JSF 2.0 support. This is full integration, not just compatibility. This means we will be leveraging the new features like the event system, behaviors, base AJAX support, and component model. As you've come to expect we'll also be innovating and adding to the base JSF features. Some of these include dynamic resource support, and event driven AJAX updates.
Event Driven Rendering or updates in an interesting idea and would allows components to automatically (via model update events) register to be rerendered. This would mean if data gets updated the component is automatically rerendered on the client side with the next ajax request. This is still in the investigation phase and not committed to.
We wanted the build system for 4.0 to be easier to use, and module in nature. There will also be cleaner version management, and partitioning so working with just one or two parts of the framework will be easier and less cumbersome.
We are also going to streamline the CDK and remove all proprietary file formats to make it easier to work with. With JSF 2.0 there are fewer artifacts required for component creation and we are following suit. The new CDK will by more annotation and convention driven, as well integrate easier with tooling.
- XHTML file to generate renderer
- Base component classes for functionality
- Optional XML configuration file
- No more proprietary file formats
- Better tool support
We will also be going through the whole component library and reviewing each for functionality, consistency, and performance. If it makes sense we'll combine components, or deprecate unneeded components and API. If it is unavoidable we may remove component and code now. This means changes to TLDs, XSDs, and APIs are possible. As always there will be more information on this in the meeting minutes, wiki, and forums.
It was not all fun - this is where we spent
25-30 hours in 2.5 days.
Ilya Shaikovsky and Anton Belevich starting the
- XSDs for component relationships and file formats to make tooling support easier
- JSP support will be depricated, just like with JSF 2.0. We will make a best effort to support all features with JSP pages and this should not be a problem, but it will be a lower priority.
- JSF 2.1 features and discussions - see Seam's JSF 2.1 site for details
- QE will have a new focus on automation using Selenium and JSFUnit so that we can improve quality and performance across the many browser, OS, and container combinations supported by Richfaces.
- Documentation will also be getting a fresh look and review. We want to make it easier to find the information you need.
We have a new RichFaces project page under development. It will have a similar layout as the new JBoss Tools project site. This is in development now and hope to have something soon.
Updating the RichFaces wik to make it easier to find what you need
- Updated FAQ in the wiki
How to get involvedand
- Meeting transcripts and details
- Security issue tips and reporting
- Jira policies & usage
We have also created a new jira project to help separate out RichFaces Planning jiras from the actual changes in the releases. This will make it easier to track your issues and and get a sense of the scope of the releases. We'll be rolling this out in the next several weeks.
All work and no play makes for a boring project. We took an afternoon and explored the Starobrno brewery, walked around Spilberk Castle and enjoyed a fair amount of local food (meat) and beverage (beer).
If you are looking for more details they are either in RichFaces wiki, or RichFaces Design Forum. For even more details we meet publicly every week on IRC. For details on the meeting and agenda, minutes, and transcripts see RichFaces Team Meeting wiki page, and don't forget to follow the project on twitter
Comments, ideas and contributions welcome so please join in!
Overall it was a lot of work and a lot of fun, and I want to thank the people in the Brno office, the RichFaces team, Pete Muir, and Rodney Russ for making it a great and successful meeting, and to Marek Novotny from the Seam team for setting up the team events!
The RichFaces Team will be in Brno Czech Republic for a rare face-to-face meeting from June 15th to June 17th. We will be discussing the future of RichFaces including RichFaces 4.0.0/JSF 2.0 & 3.3.2 releases.
If there is enough local interest we may be able to set up a night out with the community at a local establishment. If you are interested and can make it to Brno one of those nights post a comment or head over to the RichFaces User Forum.
Hope to hear from you!!
|The RichFaces team is proud to announce the release of 3.3.1.GA. There are several new components, lots of stabilization, and 1100+ jiras resolved. We also have a new photo album example to explore and build from.|
There several new component in 3.3.1. The most anticipated are the new layout components, and themes, but we also added a new <rich:colorPicker/> in the release as well.
- <rich:page/> easily setup your page structure such as header, footer, content, and sidebar.
- <rich:layout/> and <rich:layoutPanel/> nestable page layouts using Yahoo's UI CSS Grid under the hood to providing lots of flexibility.
We also added a new concept called themes which are predefined and packaged layouts that interact with the tags above. This makes it easy to experiment and adjust your layout in a similar way that skins make it easy to swap your look & feel. We also created maven archetypes and CDK goals to easily create your own themes.
As I said over 1100 jira issues were resolved - the details can be found in the release notes.
Some of the more popular are:
- JQuery script updated to 1.3.2 version
- Maven Resource Dependency Plugin
- Calendar lazy loading implemented RF-6884
- Tree Adaptors configurable recursion order RF-6639
- rich.isUserInRole() added for security integrations Acegi and etc..). RF-6551
- Queue mechanism updated RF-5788
- Modal Panel DOM reposition made configurable. RF-5588
- limitToList server side optimizations RF-5838
We also extended and stabilized our selenium based automation suite which will ensure high quality and better environment coverage moving forward.
The team also worked hard to get a full scale demo application ready. This is a separate download (see the links at the bottom), and contains best practices and example of RichFaces in action. It includes drag-n-drop, file upload, wysiwyg editor components and more. We will be hosting a version of it online soon, so keep an eye out on the project page, or watch the RichFaces Twitter account.
The focus of the RichFaces team will be on RichFaces 4.0 which will be fully integrated with JSF 2.0 and also be redesigned for consistency, performance, and ease of use. All of our meetings and plans are open to all so please join us. See RichFaces Team Meeting wiki, and/or the RichFaces 4.0 Planning wiki pages for more information.
We will also be having a RichFaces 3.3.2 release sometime in the summer that will be strictly a bug fix release.