The second beta release of RichFaces 4.5 (4.5.0.Beta2) has been released. This release focuses on stabilizing RichFaces 4.5.0.Beta1 with a number of bug fixes. Read below for a summary of the issues resolved.
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.5.0.Beta2. For more information on setting up a RichFaces 4 application, refer to our getting started guide.
Release Notes
Bug
-
RF-11090 - rich:collapsibleSubTable cannot be nested
-
RF-11656 - Nested collapsibleSubTable always expanded
-
RF-12399 - Showcase: rich:contextmenu cannot find image
-
RF-13081 - Facets "disabled" not working for dataScroller
-
RF-13645 - contextMenu for extendedDataTable breaks after ajax render of contextMenu
-
RF-13655 - Popup Panel autosize does not work when its content is dynamically updated
-
RF-13708 - Photoalbum: refresh over index page throws error
-
RF-13722 - Document CDK Maven Changes for 4.5
-
RF-13747 - a4j:commandLink does not have a default event name
-
RF-13781 - Enable RichFaces to be built with the jdk6
-
RF-13783 - Placeholder: attribute styleClass doesn’t work inside inplace input and inplace select
-
RF-13787 - Push with EAP 6.3 not using WebSockets
-
RF-13790 - Showcase - dataTable Styling example - broken styling after built in sorting/filtering is enabled
-
RF-13791 - Push in Showcase with EAP 6.2
-
RF-13794 - FileUpload serverError on upload on Wildfly
-
RF-13795 - RichFaces build is broken when running integration with release profile
-
RF-13798 - Showcase: select sample is not working [myfaces]
-
RF-13803 - Push on Tomcat 8: Unable to load current conversations from the associated request
-
RF-13804 - rich:select selectFirst attribute not working
-
RF-13814 - Photoalbum cannot be deployed to EAP
-
RF-13817 - Both the Component Reference are missing the Revision History appendices
Enhancement
Feature Request
Next steps
Work on RichFaces 4.5.0.CR1 is currently underway. Look for this first CR release to follow in the next week or two.
Share this post
Twitter
Google+
Facebook
Reddit
LinkedIn
StumbleUpon
Pinterest
Email