ICEfaces
  1. ICEfaces
  2. ICE-1869

ICEfaces Portlets from different WARs can't co-exist on the same Portal page

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.6, 1.6.1
          • Fix Version/s: 1.7DR#3, 1.7
          • Component/s: Bridge, Framework
          • Labels:
            None
          • Environment:
            ICEfaces 1.6 / Tomcat 6.0.13 / Liferay 4.3.1 (trunk)
          • Affects:
            Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration

            Description

            Attached you will find two portlets:

            1. sample-icefaces-sun-portlet

            2. sample-icefaces-sunny-portlet

            The only difference between these two portlets is the portlet name. All else is the same.

            Now, I can put two of #1 on the same page, or two of #2 on the same page, and everything works great (multiple instances of the same portlet)

            But when I put #1 and #2 on the same page, only one of them will "win" and work. The other one causes a "User Session Expired" type of error message to appear.

            The attached portlets are meant to be unzipped and placed directly into the "webapps" folder of a Liferay 4.3.1 / Tomcat 6.0.13 bundle.

              Issue Links

              depends on

              Bug - A problem which impairs or prevents the functions of the product. ICE-1675 Framework specific ID (ICEfaces ID and view number) handling breaks multiple portlets on a page

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Neil Griffin added a comment -

                BTW, I forgot to mention that my best guess is that this has something to do with the fact that the contents of the JobApplication.jspx file is the same for each portlet. Perhaps there is a conflict of "id" attribute values.

                Under IE7, the "User Session Expired" message occurs. Under FireFox, nothing happens – meaning, when I tab between fields, the partialSubmit features don't work and validation does not take place.

                Show
                Neil Griffin added a comment - BTW, I forgot to mention that my best guess is that this has something to do with the fact that the contents of the JobApplication.jspx file is the same for each portlet. Perhaps there is a conflict of "id" attribute values. Under IE7, the "User Session Expired" message occurs. Under FireFox, nothing happens – meaning, when I tab between fields, the partialSubmit features don't work and validation does not take place.
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Currently, when 2 ICEfaces portlets from different WARs are added to the same Portal page, the former ICEfaces Portlet will break and the latter will work (win). Looking at the HTTP logs, both ICEfaces Portlets end up using the same ICEfaces ID as well as the same context paths.

                Show
                Jack Van Ooststroom added a comment - Currently, when 2 ICEfaces portlets from different WARs are added to the same Portal page, the former ICEfaces Portlet will break and the latter will work (win). Looking at the HTTP logs, both ICEfaces Portlets end up using the same ICEfaces ID as well as the same context paths.
                Hide
                Permalink
                Mike Lawrence added a comment -

                I just closed a duplicate issue I created in Liferay
                http://support.liferay.com/browse/LEP-3967

                You may want to use my WARs as well to verify the fix.

                Show
                Mike Lawrence added a comment - I just closed a duplicate issue I created in Liferay http://support.liferay.com/browse/LEP-3967 You may want to use my WARs as well to verify the fix.
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Changed Fix Version to 1.7DR#3

                Show
                Jack Van Ooststroom added a comment - Changed Fix Version to 1.7DR#3
                Hide
                Permalink
                Jack Van Ooststroom added a comment -

                Documentation needs to be updated for this as well!

                Show
                Jack Van Ooststroom added a comment - Documentation needs to be updated for this as well!

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: