Tapestry
  1. Tapestry
  2. TAPESTRY-1252

Setting updateComponents in DirectLink forces async execution

    Details

      Description

      If that's the intended behavior, we should document it.

        Activity

        Hide
        Norbert Sándor added a comment -

        I just wanted to report this

        I think it would be better if binding updateComponents would not force async execution:

        • I think semantically it would be more correct (and easier to remember)
        • often I want to turn off async requests for testing purposes, in these cases I have to set async to false AND remove the updateComponents binding as well
        Show
        Norbert Sándor added a comment - I just wanted to report this I think it would be better if binding updateComponents would not force async execution: I think semantically it would be more correct (and easier to remember) often I want to turn off async requests for testing purposes, in these cases I have to set async to false AND remove the updateComponents binding as well
        Show
        Andreas Andreou added a comment - http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-framework/src/java/org/apache/tapestry/engine/DirectServiceParameter.java?r1=437456&r2=478737 Jesse, you decide i just find this counter-intuitive + agree with norbert arguments
        Hide
        Andreas Andreou added a comment -

        Documented.

        Show
        Andreas Andreou added a comment - Documented.

          People

          • Assignee:
            Andreas Andreou
            Reporter:
            Andreas Andreou
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development