5 Replies Latest reply on May 11, 2008 8:14 AM by pavel.myshkin

    a4j bridge

      I am trying to use the new bridge with ajax/rich jsf (no faclets but jsp).
      I get this exception:
      java.lang.ClassCastException: org.jboss.portlet.JBossRenderRequest
      What is the required configuration for the new bridge? examples are for faclets and the demo application is for seam+rich.
      I played with the configuration and got my page, but when I tried to submit it I got exception that handler could not retrieve view for my jsp.

        • 1. Re: a4j bridge
          den74

          hi,

          i have the same problem, have you found a solution?
          I got it trying to use a custom class that override portlet life cycle methods (doView, processAction) doing something before to call the parent methods... nothing special


          My env
          --------
          jboss portal 2.6.4 (boundled with jb as)
          richfaces 3.2.0GA
          portletbridge 1.0.0 B2


          thanks to anyone suggests a solution

          • 2. Re: a4j bridge
            den74

            i think i found the problem: i'm using jsf 1.2 architecture with jsp and i think it is not possible into portal 2.6.4/2.6.5 because of the application server (on tomcat jsf 1.2 and jsp are enabled only on 6 version).

            I tryed a simple test with facelet instead of jsp and it works, so maybe using facelets is the only way to work with jsf ri 1.2, richfaces 3.2 and portal 2.6.4/2.6.5 ...

            Hope this info will be useful for others

            • 3. Re: a4j bridge
              wesleyhales

              Yes you are correct, this is a feature only for Servlet 2.5 as required by JSF 1.2.

              • 4. Re: a4j bridge
                wesleyhales

                if you do meet the above criteria and want to use jsp, you must coment out the Facelet View Handler in web.xml. And change extension type to *.jsp.

                • 5. Re: a4j bridge

                  Generally if you get a ClassCastException regarding JBP core classes then it means (most of the time) that you have included the JBP jars, which are the dependencies in your MyEclipse, in to the WAR.

                  Hope this helps.