You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ron Piterman (JIRA)" <ta...@jakarta.apache.org> on 2006/02/03 11:43:03 UTC
[jira] Created: (TAPESTRY-856) lazy initialization of abstract
properties
lazy initialization of abstract properties
------------------------------------------
Key: TAPESTRY-856
URL: http://issues.apache.org/jira/browse/TAPESTRY-856
Project: Tapestry
Type: Improvement
Versions: 4.1
Reporter: Ron Piterman
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Updated: (TAPESTRY-856) lazy initialization of abstract
properties
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-856?page=all ]
Jesse Kuhnert updated TAPESTRY-856:
-----------------------------------
Fix Version/s: 4.1.2
> lazy initialization of abstract properties
> ------------------------------------------
>
> Key: TAPESTRY-856
> URL: http://issues.apache.org/jira/browse/TAPESTRY-856
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.1
> Reporter: Ron Piterman
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-856) lazy initialization of abstract
properties
Posted by "Brian K. Wallace (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-856?page=all ]
Brian K. Wallace updated TAPESTRY-856:
--------------------------------------
Component: Framework
> lazy initialization of abstract properties
> ------------------------------------------
>
> Key: TAPESTRY-856
> URL: http://issues.apache.org/jira/browse/TAPESTRY-856
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.1
> Reporter: Ron Piterman
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-856) lazy initialization of abstract
properties
Posted by "Ron Piterman (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484933 ]
Ron Piterman commented on TAPESTRY-856:
---------------------------------------
this has nothing with HOW the expresion is evaluated, but WHEN it is evaluated and when the property is being reset (to null) - therefore has also nothing with 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-856) lazy initialization of abstract
properties
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org