Struts 2
  1. Struts 2
  2. WW-1894

struts2-portlet-2.0.6 ajax example not working

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.6
    • Fix Version/s: Future
    • Component/s: Example Applications
    • Labels:
      None
    • Environment:

      WebLogic Portal Server 9.2, Windows XP, Internet Explorer 6.0, Java 1.5.0_06

      Description

      1. Tags containing 'nested' quotation marks yield some sort of "attribute not recgnized" error. e.g., href="<s:url action="ajaxData"/>" is a problem, so I switched that to an EL expression as illustrated in the documentation:

      <s:url id="ajaxExampleAction" action="ajaxData" />

      href="%

      {ajaxExampleAction}"

      which seems to work, except that


      2. The inclusion of the Ajax result on more than one place crashes my IE 6.0 browser pretty consistently (I don't have another browser to test with yet, unfortunately). e.g.,

      <s:div id="once" href="%{ajaxExampleAction}

      " ...>

      <s:div id="twice" href="%

      {ajaxExampleAction}

      " ...>

      is a problem. Hacked the example to include just a single ajax-enabled div and

      3. it all seems to work, except that the portal has aggregated the content instead of allowing the browser to do it in-place. i.e., the ajaxData.jsp content is surrounded by portal markup (title bar, window state controls, etc.)

        Issue Links

          Activity

          Hide
          musachy added a comment -

          closing ajax related bugs

          Show
          musachy added a comment - closing ajax related bugs
          Hide
          Nils-Helge Garli added a comment -

          Yes, Ajax still doesn't work with the portlet plugin.

          Show
          Nils-Helge Garli added a comment - Yes, Ajax still doesn't work with the portlet plugin.
          Hide
          Don Brown added a comment -

          Nils, can you confirm this is still a bug?

          Show
          Don Brown added a comment - Nils, can you confirm this is still a bug?
          Hide
          Don Brown added a comment -

          Moving to 2.1.0 because the ajax and portlet code have been moved into their own plugin, so the fix will be quite different and not worth doing on the 2.0.x branch, IMO.

          Show
          Don Brown added a comment - Moving to 2.1.0 because the ajax and portlet code have been moved into their own plugin, so the fix will be quite different and not worth doing on the 2.0.x branch, IMO.
          Hide
          James Holmes added a comment -

          Moving to 2.0.10 so that 2.0.9 can be released.

          Show
          James Holmes added a comment - Moving to 2.0.10 so that 2.0.9 can be released.

            People

            • Assignee:
              Unassigned
              Reporter:
              Bill Bruyn
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development