Tapestry
  1. Tapestry
  2. TAPESTRY-856

lazy initialization of abstract properties

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 4.1
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None

      Description

      when using parametr bindings, one can use ognl, (which is slowmotion), to navigate through an object graph.
      A (fast) alterntive is use an abstract property with an initializer method:

      component A :

      { @InitialValue("getXFromDatabase()") public abstract X getX(); }

      now if X is dependant on the bindings of component A, this will not work, since X property will often be initialized before the bindings are available - or sometimes, also when not posssible to get, because, say, component A is inside an If which does not allow it to render, if unable to... (say x ID is not given...)

      please add a lazy initialization option for abstract properties to allow this be treated more smoothly...

        Activity

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Ron Piterman
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development