Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None

      Description

      I have a contrib:tableRows component that binds the EvenOdd class like this:

      <component id="tableRows" type="contrib:TableRows">
      <binding name="class" expression="beans.evenOdd.next"/>
      <binding name="row" expression="currentRow"/>
      </component>

      However the evenOdd class was never getting instantiated/processing on each row in the table.

      I looked into my .html page and noticed that I had something like this:

      <tr jwcid="tableRows" class="odd">

      but when I took the class attribute out of my html the evenOdd bean got instantiated and processing. So it looks like there is an issue of binding a bean to an attribute if it already exists in a .html page. This page is part of an app I am migrating from 3.0, in which the evenOdd bean processed properly with the class attribute in the .html page.

      Is this an issue with contrib:tableRows or bindings in general if you attempt to bind to an html attribute that is already set?

      scott

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Scott Walter
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development