14 Replies Latest reply on Mar 5, 2012 12:30 PM by apodgorsek

    Opinion on Rich Faces 4

    kshanth

      Hi Friends, Please share your thoughts about RF 4.   Hope it help others

       

      AreaOpinion
      JSF 2 SupportNice 
      AJAX Enabled ComponentsCool
      Developer GuidePoor
      JSR 303 Bean ValidationNo idea
      Advanced queueingVery useful

      Especially ignoreDupResponse

      Push componentVery nice, it helps to perform realtime client side updates
      Component Development KitNo idea
      Broad Cross-browser supportNot sure, what is new
      Tooling support Intellij, NetBeans, eclipseNice, it helps easy development
      3.3.x - 4.x Migration3.3.x have many components, which is not avilable in 4.x. 
        • 1. Opinion on Rich Faces 4
          kshanth

          There is no built in support for dataTable lazy loading.You have to stick to workarounds from long time.  

          Look at the primefaces support http://www.primefaces.org/showcase/ui/datatableLazy.jsf

          • 2. Opinion on Rich Faces 4
            kshanth

            DataTable sortBy is not working. you hav to use  a4j:commandLink to achieve this

            • 3. Opinion on Rich Faces 4
              ilya_shaikovsky

              There is no built in support for dataTable lazy loading.You have to stick to workarounds from long time.

               

              Look at the primefaces support http://www.primefaces.org/showcase/ui/datatableLazy.jsf

              ExtendedDataModel impls allows the same. And ArrangeableDataModel (ExtendedDataModel which implements Arrangeable) do the same + allows filtering with sorting on the custom model. In-db sorting/filtering/pagging using our Arrangeable model sample - comming soon.

               

              DataTable sortBy is not working. you hav to use  a4j:commandLink to achieve this

              Convenient API usually is more important that controls. Sorting/Filtering works the same as in 3.3.x but just has no out-of-the-box controls which b.t.w. was often discussed as not 100% convenient (that's why we postponed and will redesign). You could just implement sorting in a 3 minutes using call to sort() JS API on the table and it will be sorted. Or use a4j:commandLink if want to customize request.

              • 4. Re: Opinion on Rich Faces 4
                kshanth

                Ilya Shaikovsky wrote:

                 

                There is no built in support for dataTable lazy loading.You have to stick to workarounds from long time.

                 

                Look at the primefaces support http://www.primefaces.org/showcase/ui/datatableLazy.jsf

                ExtendedDataModel impls allows the same. And ArrangeableDataModel (ExtendedDataModel which implements Arrangeable) do the same + allows filtering with sorting on the custom model. In-db sorting/filtering/pagging using our Arrangeable model sample - comming soon.

                 

                I have tried with in-db sorting/filtering/pagging using Arrangeable model as a sample, it works some extend but sorting and filtering is not happening. Look at the attachement and suggest me.

                • 5. Re: Opinion on Rich Faces 4
                  kshanth

                  There is no rich:layout support in 4.x. If you want, use jQuery based layout. After some struggle succeed with UI:Layout

                  Look at the attached sample

                  • 6. Re: Opinion on Rich Faces 4
                    ilya_shaikovsky

                    In case of implementation problems

                    I have tried with in-db sorting/filtering/pagging using Arrangeable model as a sample, it works some extend but sorting and filtering is not happening. Look at the attachement and suggest me.

                    not looks good to say

                     

                    There is no built in support for dataTable lazy loading.You have to stick to workarounds from long time.

                     

                     

                    Rising the post with asking for exmplanations would be much better.

                     

                    P.S. will review your sample later. Now working on the same demo and want to publish it to community review faster.

                    • 7. Re: Opinion on Rich Faces 4
                      ilya_shaikovsky

                      There is no rich:layout support in 4.x. If you want, use jQuery based layout. After some struggle succeed with UI:Layout

                      Look at the attached sample

                      having large experinece with 3.3.x users opinions could only say that those components has lower priority because our previous layouts were not used much. Users still preferred to use plain Y! or jQuery(to get more control). So that's why postponed and want to revise to make more convenient/rich.

                      • 8. Opinion on Rich Faces 4
                        lfryc

                        Using custom layouts with Composite Component facets feature should not problem in JSF 2 anymore. You will get much more freedom over resultant layout.

                        • 9. Re: Opinion on Rich Faces 4
                          folk21

                          Hello!

                           

                          In RichFaces 3 was a possibility to handle errors and session expiration on client side using A4J.AJAX

                          Like this:

                          A4J.AJAX.onExpired = function(loc, expiredMsg){

                          ...

                          }

                          When I try to use it in RichFaces 4 I get JavaScript error: A4J is not defined

                           

                          Which approach should be used in RichFaces 4 in order to handle session expired case (instead of A4J.AJAX.onExpired) and to handle errors (instead of A4J.AJAX.onError)?

                          • 10. Re: Opinion on Rich Faces 4
                            ilya_shaikovsky

                            It's just not RF responsibility also.. In JSF 2 when basic Ajax standartized - you need to use JSF 2 Exception Handling feature at server side and onError handler on client side. refer to basic JSF 2 docs to get more info.

                            • 11. Re: Opinion on Rich Faces 4
                              jbalunas

                              Hi Shanth,

                               

                              I think we could do a better job of demonstrating some of the features we already have, because as Ilya said our extended data table already supports many of the features you brought up.

                               

                              As for JSR-303 bean validation, you said "no idea".  Is that just because you have not used it yet?

                               

                              -Jay

                              • 12. Opinion on Rich Faces 4
                                kshanth

                                I think we could do a better job of demonstrating some of the features we already have,

                                Jay, I agree with you, but think about the users migrating from 3.x to 4.x. There is no backward compatability, some of the components not available.

                                 

                                we already have, because as Ilya said our extended data table already supports many of the features you brought up.

                                May be few things takes 10 - 15 mins to implement on their own, but searching for the API takes long time. Look at this sample, this won't work in 4.x. Also you will not find any sample or documentation to migrate. For you guys it takes less than 10 mins to write a sample. Hope we get one soon.

                                 

                                As for JSR-303 bean validation, you said "no idea".  Is that just because you have not used it yet?

                                I have not used it.

                                • 13. Opinion on Rich Faces 4
                                  ilya_shaikovsky

                                  http://jira.jboss.org/browse/RF-10845 - watch that to check when resolved.

                                  • 14. Re: Opinion on Rich Faces 4
                                    apodgorsek

                                    You should make an example for database pagging on all the components that you support.

                                     

                                    Is there any samples for extended datatable?