Thursday, October 18, 2012

RichFaces 4.2.3.Final Release Announcement

RichFaces

RichFaces 4.2.3.Final has been released. This Final release is a re-tag of the 4.2.3.CR1 release as no blocking issues were found by either our QE team, nor by the community.

The RichFaces 4.2.3.Final release is purely a bug-fix release, with a focus on compatibility between RichFaces and the JBoss Portlet Bridge. I’ll refer you to the RichFaces 4.2.3.CR1 release blog for details of the release, with a special highlight paid to the contributions from the JBoss Portal Bridge team, and contributions from community members.

To try out this release: You can download the distribution directly, or for maven users, increment the RichFaces version in your pom.xml to 4.2.3.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Release Notes:

To re-cap, the changes in the 4.2.3.Final release compared to the 4.2.2.Final release include:

Bug

  • [RF-10758] – Input fields in popupPanel lose focus
  • [RF-10980] – Impossible to set tabindex of input inside rich:popupPanel
  • [RF-11051] – a4j.version does not work
  • [RF-11104] – rich:inputNumberSlider slider position is affected by css position attribute of containing element
  • [RF-12113] – rich:inputNumberSpinner minValue and maxValue being ignored after second request
  • [RF-12114] – Richfaces 4.2 rich:autocomplete don't fire ajax on blur event
  • [RF-12221] – rich:orderingList: fix VDL-DOC of @listHeight, @maxListHeight, @minListHeight, @listWidth
  • [RF-12256] – DragAndDrop + position: absolute results in broken positioning
  • [RF-12273] – rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL
  • [RF-12424] – Showcase contains Servlet specific code
  • [RF-12425] – Showcase fails to load SyntaxHighlighter scripts when Require.js is present
  • [RF-12476] – Resource Name in mapping for two menu images is incorrect

Enhancement

  • [RF-12343] – Problem when saving form with rich picklist inside composite component

This is very much a community driven release. Thanks guys, you rock!

Stay Tuned for 4.3.0.M2

The QA process for the 4.3.0.M2 release is about to begin, with a release as soon as QA is done. So stay tuned, as there is lots more great stuff to come!


Wednesday, October 10, 2012

RichFaces 4.2.3.CR1 Release Announcement

RichFaces

I am happy to announce that the first candidate release of RichFaces 4.2.3 (4.2.3.CR1) is now available. This is purely a bug-fix release, with a focus on compatibility between RichFaces and the JBoss Portlet Bridge.

To try out this release: You can download the distribution directly, or for maven users, increment the RichFaces version in your pom.xml to 4.2.3.CR1. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Portlet Bridge Fixes

RichFaces aims to be a container agnostic project, working in Servlet containers, Java EE implementations, and Portals, all from multiple vendors. Of course keeping up with bugs and fixes across all these deployment environments is a lot of work, so we naturally tend to focus our efforts on certain specific environments. As such, nothing makes us happier then receiving github pull requests addressing compatibility issues between RichFaces and one of these deployment containers.

This is precisely what Ken Finnigan of the Portal Bridge team has done, identifying and resolving a number of issues with RichFaces when running in a Portlet environment. Unfortunately a number of servlet specific references leaked through in some of our implementations, but Ken has done an excellent job rounding these up, and replacing them with the appropriate JSF abstraction, ensuring RichFaces components work equally well in servlet and portlet environments. Great job Ken!

Community Contributions

I’d also like to call out , Bernard Labno, Christian Kaltepoth, and Luca Nardelli for the bugs they fixed and submitted as github pull requests. RichFaces is a very much a community project, and it’s in part contributions like these that keep the project healthy and moving forward. Thanks guys — and keep those pull requests coming!

Release Notes:

Specific issues resolved with this release include:

Bug

  • [RF-10758] – Input fields in popupPanel lose focus
  • [RF-10980] – Impossible to set tabindex of input inside rich:popupPanel
  • [RF-11051] – a4j.version does not work
  • [RF-11104] – rich:inputNumberSlider slider position is affected by css position attribute of containing element
  • [RF-12113] – rich:inputNumberSpinner minValue and maxValue being ignored after second request
  • [RF-12114] – Richfaces 4.2 rich:autocomplete don't fire ajax on blur event
  • [RF-12221] – rich:orderingList: fix VDL-DOC of @listHeight, @maxListHeight, @minListHeight, @listWidth
  • [RF-12256] – DragAndDrop + position: absolute results in broken positioning
  • [RF-12273] – rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL
  • [RF-12424] – Showcase contains Servlet specific code
  • [RF-12425] – Showcase fails to load SyntaxHighlighter scripts when Require.js is present
  • [RF-12476] – Resource Name in mapping for two menu images is incorrect

Enhancement

  • [RF-12343] – Problem when saving form with rich picklist inside composite component

What’s next?

Be sure to take this candidate release for a spin, and report back any regressions. We are expecting the 4.2.3.Final release to simply be a re-tag of the CR1 release, barring any unforeseen blockers.

In the mean time we are hard at work on our the 4.3 release train, and are working on having a 4.3.0.M2 release available hot-on-the-heels of this 4.2.3 release.


Wednesday, September 7, 2011

Seam Faces Community Hack Night

This week’s Seam 3 Community hack night is centered around Seam Faces. This is a great chance to mingle with some CDI/JSF developers on IRC, and get your fingerprint into the Seam Faces DNA! Whether you have your own itch you want to scratch, a long-standing bug you want to see resolved, or implement a new feature altogether, we’ve got plenty of low hanging fruit ripe for the picking!

In preparation for the hack-a-thon, I’ve given the Seam Faces JIRA issues a once-over. I’ve collected a number of issues that I feel are ready to be resolved into a JIRA version calles 3.1.0-Tracking. I’d like to highlight a few of the issues here, and perhaps motivate you to come join us at the hack-a-thon to resolve some of them!

SEAMFACES-122: Type safe navigation!

Of all the low-hanging fruit, this one has to be the juiciest! Implement a Navigator utility class to map the @ViewConfig enums to their String @ViewPattern’s for use in JSF navigation. Imagine using your IDE to find all usages of one of your views – type safety FTW!

SEAMFACES-26: Implement global protection against XSRF attacks

Help the community of Seam 3 developers make their apps more secure by implementing a scheme to protect against XSRF attacks! Think hidden form field, view state and a random number generator.

SEAMFACES-28: ObjectConverter and EntityConverter

Let’s resurrect the Entity Converter from Seam 2. The EntityConverter is persistent context aware, and will use the primary key of your JPA/Hibernate entities to handle JSF Conversion.

SEAMFACES-150: Refactor BeanManagerUtils to make use of Solder’s BeanManagerLocator

Are you aware with the Seam Solder API? Want to learn more about how to wield this powerful tool? Here’s a refactoring that will surely get you more comfortable with how to use Solder.

SEAMFACES-6: s:debug

This issue is very well documented in JIRA, and just needs someone to put the pieces together. What a great tool to add to your arsenal once complete!

SEAMFACES-185: Add support for activating beans based on the JSF project stage

Christian Kaltepoth has done a great job with this issue, but we’ve got a tough nut to crack. How to parse the web.xml before the Servlet Context is available? If you got some ideas here, help us bring this one across the finish line.

SEAMFACES-184: Extend an example to demonstrate events propagation features

Familiar with Seam Faces, but don’t feel up to hacking on the core? How about writing an example application, to demonstrate some of Seam Faces’ cool features?

SEAMFACES-152: Create documentation for using Seam Catch in Faces

Another great way to contribute to the project, without writing a single line of code is to contribute docs! Help other Seam 3 devs figure out what you already know!

These are just a few of the issues ready to be solved during the hack night. So drop by on IRC, and give us a hand squashing some issues. At the very least, I’m sure you’ll have fun!