7 Replies Latest reply on Apr 17, 2008 3:47 AM by Tomislav Jakopec

    3.2.0 BUG or my fault?

    Tomislav Jakopec Novice

      In my app is code

      <t:selectBooleanCheckbox value="#{izvjestajZaposlenik.trenutniDatum}">
      <a:support eventsQueue="red" event="onclick"
      actionExpression="#{izvjestajZaposlenik.setTrenutniDatum(!izvjestajZaposlenik.trenutniDatum)}"
      reRender="datumVazenja" />
      </t:selectBooleanCheckbox>
      


      and its working fine with 3.1.4. GA

      now with 3.2.0 first probleme is actionExpression. OK I put action. That is solved. Now problem is



      org.apache.jasper.JasperException: /kadrovska/maticni/zaposlenik/izvjestaj/IzvediIzvjestaj.jsp(128,8) The function setTrenutniDatum must be used with a prefix when a default namespace is not specified


      Is this bug or should I change my code???

        • 1. Re: 3.2.0 BUG or my fault?
          Tomislav Jakopec Novice

          On JIRA (http://jira.jboss.com/jira/browse/RF-2320) this problem is ignored. Then must be my fault. But what??? Have somebody else same problem?

          • 2. Re: 3.2.0 BUG or my fault?
            <todo> <todo> Newbie

            Have you read comments on issue?

            • 3. Re: 3.2.0 BUG or my fault?
              Tomislav Jakopec Novice

               

              "rsinus" wrote:
              Have you read comments on issue?

              Yes, I did!
              OK, I will put together sample project and attach it

              • 4. Re: 3.2.0 BUG or my fault?
                Alex Alvarez Newbie

                Hi,

                i'm having a similar bug, i think the problem could be related to incompatibilites with Tomahawk, specially when using Facelets.

                Here for instance when I use <t:selectItems ...>, all ajax requests stopped working. I had to remove all tomahawks tags in order to be able to use richfaces, but t:selectItems is such a great tag... what a shame :-(

                <h:selectOneListbox value="#{analystMatrixManager.selectedMatrix}" size="10" styleClass="windowList" converter="javax.faces.Long">
                 <t:selectItems value="#{analystMatrixManager.matrices}" var="matrix" itemLabel="#{matrix.publishId} #{matrix.publishDate} #{matrix.userNickname}" itemValue="#{matrix.publishId}" />
                </h:selectOneListbox>


                Although i presume that in this case the fault might lie more with Tomahawk, the best would be a compatibility test suite with other JSF component frameworks.

                Alex


                • 5. Re: 3.2.0 BUG or my fault?
                  Tomislav Jakopec Novice

                  3.2.0 is full of bugs :(
                  I am waiting SP1.
                  Only problem is that most off bugs where here before announcing 3.2.0
                  I try on daily basis SNAPSHOT and test it on our application. All bugs are reported.

                  What bothers me is that RF team is focusing on new features, but its very hard to get them to fix something.

                  • 6. Re: 3.2.0 BUG or my fault?
                    Sergey Smirnov Master

                     

                    "tjakopec" wrote:

                    What bothers me is that RF team is focusing on new features, but its very hard to get them to fix something.


                    During the whole development cycle of RichFaces 3.2.0, we:
                    created new components: 6
                    added new feature: 2
                    fixed bugs (resolved jira issues): 1,359

                    Mathematically speaking, 1,359 is greater than 8 . Right?


                    When we joined Jboss one year ago, RichFaces had 18 components. The most complicated component was suggestionBox. About 20 guys in the RichFaces team (including PM, TWs, QAs and one civilian).

                    Now we have more than 80 components. 30% of then are more complicated than suggestionBox. RichFaces team ..... 20 guys.

                    67 jira issues are resolved with status "done" for the last 2 weeks (since GA release)
                    RichFaces 3.2.0 SR1 was released yesterday with most critical issues closed.
                    RichFaces 3.1.5 CR1 was released yesterday. It is under QA process right now. Release is scheduled for next week.
                    RichFaces 3.2.1 CR1 is going to be released later this week. Release is scheduled for the beginning of May.


                    • 7. Re: 3.2.0 BUG or my fault?
                      Tomislav Jakopec Novice

                       

                      "SergeySmirnov" wrote:


                      During the whole development cycle of RichFaces 3.2.0, we:
                      created new components: 6
                      added new feature: 2
                      fixed bugs (resolved jira issues): 1,359

                      Mathematically speaking, 1,359 is greater than 8 . Right?


                      That is all correct. Don't get me wrong, we like FR components. I am only frustrated because off this one bug we cannot start use 3.2.0. And 3.2.0 is good, actual excellent!


                      "SergeySmirnov" wrote:

                      When we joined Jboss one year ago, RichFaces had 18 components. The most complicated component was suggestionBox. About 20 guys in the RichFaces team (including PM, TWs, QAs and one civilian).

                      Now we have more than 80 components. 30% of then are more complicated than suggestionBox. RichFaces team ..... 20 guys.

                      67 jira issues are resolved with status "done" for the last 2 weeks (since GA release)
                      RichFaces 3.2.0 SR1 was released yesterday with most critical issues closed.
                      RichFaces 3.1.5 CR1 was released yesterday. It is under QA process right now. Release is scheduled for next week.
                      RichFaces 3.2.1 CR1 is going to be released later this week. Release is scheduled for the beginning of May.


                      I can tell that you are "upset" because my remark, no hard fillings, hope for successful cooperation in future!