We're pleased to announce that the release candidate of OmniFaces 1.5 is now available for testing.

The following items are new for this release:



Decode UIComponent children in <o:param> when no value attribute is specified (so that you can specify JSF/HTML code as outputFormat parameter)

children in when no attribute is specified (so that you can specify JSF/HTML code as parameter) Allow endusers to specify custom passthrough attributes for Html5RenderKit

Added new includeRequestParams attribute to <o:form>

attribute to <o:messages> which extends <h:messages> with support for multiple client IDs in for attribute, ability to disable HTML escaping and ability to perform markupless rendering like <ui:repeat>

which extends with support for multiple client IDs in attribute, ability to disable HTML escaping and ability to perform markupless rendering like Faces#includeCompositeComponent() to programmatically include a composite component in given parent component

to programmatically include a composite component in given parent component Add list based alternatives for the converters that automatically convert based on select items

Message interpolator for Bean Validation that allows a component's label to be inserted in the middle of a message

Added reset attribute to <o:cache> as an alternative for the programmatic resetting of a cache entry.

attribute to as an alternative for the programmatic resetting of a cache entry. Added converters for an Iterable to List and DataModel , so these can be used in <ui:repeat> and <h:dataTable>

The release candidate can be downloaded here: omnifaces-1.5-RC.jar. Please use this for testing only.

To see the API and VDL docs for this 1.5 release candidate, remove "/1.4" from the path from the current API/VDL URL.

To see the live showcase of the 1.5 release candidate, go to snapshot-omnifaces.rhcloud.com (note: the showcase doesn't necessarily show all changes)

Please take a moment to try this RC release with your projects and file an issue should you encounter any problems.

If no serious issues are discovered, we plan to promote the 1.5 RC build to final somewhere next week.

Arjan Tijms