3 Replies Latest reply on Jul 26, 2008 4:26 PM by irun5k

    LoadStyleStrategy does not work in portlet/facelet environme

    erezharari

      there is a bug on that issue - https://jira.jboss.org/jira/browse/RF-2351
      however, since richfaces 3.1.3 it has been neglected.
      we are using jboss portal + facelets + richfaces 3.2.1 and we cannot control script and style policy.

      is that bug going to be fixed anytime soon?
      otherwise we cannot use it in production and lots of effort would be lost :-(

        • 1. Re: LoadStyleStrategy does not work in portlet/facelet envir
          irun5k

          Hello, I started my project trying to use RichFaces with JBoss Portal but had to ditch the portal one week into the project. For whatever reason, loadScript doesn't work when you use RichFaces with a Portal.

          So anyway, I tell you this only to say that having a Portal in the mix only complicates an already heavy stack of technologies. And, I don't think enough people are using RichFaces with Portal for our bugs to get (first) acknowledged, and (second) fixed. Seems like the options are (1) fix the bug yourself, or (2) purchase support from RedHat/JBoss in which case hopefully your bugs get a higher priority.

          Good luck.

          • 2. Re: LoadStyleStrategy does not work in portlet/facelet envir
            erezharari

            thanks for the tip.
            so actually you say: "don't use nither RichFaces nor jboss portal"..

            • 3. Re: LoadStyleStrategy does not work in portlet/facelet envir
              irun5k

              No, I'd say to use one or the other but not both unless you have time to debug why two technologies don't work together properly.

              IMHO this is the problem with frameworks. Can't live with them, can't live without them. Users expect a rich experience now, and it just isn't feasible to built a site like this by hand coding HTML thru JSP/Velocity/etc. But these new frameworks are complex and supposed to make our lives easier, which in many ways they do. However, the further abstracted away from the details we get, the more of a world of hurt the end-developer is in when something breaks.