[
https://issues.apache.org/jira/browse/TAPESTRY-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert resolved TAPESTRY-856.
------------------------------------
Resolution: Won't Fix
Assignee: Jesse Kuhnert
I think ognl offers the best solution for this one and is also no longer a
problem wrt performance. If I'm mistaken please feel free to re-open and we can
discuss other possibilities...but obviously most will require similar logic to
that provided by ognl.
> lazy initialization of abstract properties
> ------------------------------------------
>
> Key: TAPESTRY-856
> URL: https://issues.apache.org/jira/browse/TAPESTRY-856
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.1
> Reporter: Ron Piterman
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.2
>
>
> 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...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
