Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6
    • Fix Version/s: 1.7DR#3, 1.7
    • Component/s: None
    • Labels:
      None
    • Environment:
      WinXP / Liferay 4.3.1 / Tomcat 6.0.13

      Description

      When I set the "com.icesoft" flag to true in my log4j.xml file, I see stuff like this in the Tomcat console:
      02:57:10,937 DEBUG [BridgeFacesContext:166] Cannot find clientId _sample_icefaces_sun_WAR_sampleicefacessunportlet_INSTANCE_g3Hm__id1:_sample_icefaces_sun_WAR_sampleicefacessunportlet_INSTANCE_g3Hm__id4:firstNamefrom facesMessages

      Is this a warning? Is it an error?

      Drop the attached portlet in your $HOME/liferay/deploy (aka hot-deploy) folder and it will hot-deploy itself when the portal is running. When you tab from one field to another, you will see debugs like the one mentioned above.

        Activity

        Neil Griffin created issue -
        Neil Griffin made changes -
        Field Original Value New Value
        Attachment sample-icefaces-sun-portlet-4.3.0.1.war [ 10611 ]
        Ken Fyten made changes -
        Fix Version/s 1.7DR#1 [ 10100 ]
        Assignee Priority P3
        Assignee Mircea Toma [ mircea.toma ]
        Ken Fyten made changes -
        Fix Version/s 1.7 [ 10080 ]
        Fix Version/s 1.7DR#1 [ 10100 ]
        Ken Fyten made changes -
        Assignee Priority P3
        Assignee Mircea Toma [ mircea.toma ] Deryk Sinotte [ deryk.sinotte ]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #15088 Fri Nov 02 17:08:48 MDT 2007 deryk.sinotte ICE-2017: Adjusted logic and logging call when getting FacesMessages.
        Files Changed
        Commit graph MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/context/BridgeFacesContext.java
        Hide
        Deryk Sinotte added a comment -

        This was not a functionality bug and it was not limited to the portlet environment. The logging message was at DEBUG level but the wording made it sound more ominous that it really was. It logs the information that there are no FacesMessages for each component that has an <ice:message> component associated with it. I adjusted the logic a bit and reworded the logging message to be a bit more benign. I also made it TRACE level rather than DEBUG. Resolving as fixed.

        Show
        Deryk Sinotte added a comment - This was not a functionality bug and it was not limited to the portlet environment. The logging message was at DEBUG level but the wording made it sound more ominous that it really was. It logs the information that there are no FacesMessages for each component that has an <ice:message> component associated with it. I adjusted the logic a bit and reworded the logging message to be a bit more benign. I also made it TRACE level rather than DEBUG. Resolving as fixed.
        Deryk Sinotte made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 1.7DR#3 [ 10112 ]
        Fix Version/s 1.7 [ 10080 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Fix Version/s 1.7 [ 10080 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Assignee Deryk Sinotte [ deryk.sinotte ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Neil Griffin
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: