You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Kalin Krustev (JIRA)" <de...@tapestry.apache.org> on 2008/08/21 09:50:46 UTC
[jira] Created: (TAPESTRY-2610) Allow access to component's
informal parameters
Allow access to component's informal parameters
-----------------------------------------------
Key: TAPESTRY-2610
URL: https://issues.apache.org/jira/browse/TAPESTRY-2610
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.14
Reporter: Kalin Krustev
A component may need to access all its parameters, including informal ones. This is for example when the component needs to process arbitrary list of parameters as needed when accessing a database with a query. I propose that the interface ComponentResources be extended with a method to allow such access.
--
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] Closed: (TAPESTRY-2610) Allow access to component's informal
parameters
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2610.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.15
> Allow access to component's informal parameters
> -----------------------------------------------
>
> Key: TAPESTRY-2610
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2610
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.14
> Reporter: Kalin Krustev
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.15
>
>
> A component may need to access all its parameters, including informal ones. This is for example when the component needs to process arbitrary list of parameters as needed when accessing a database with a query. I propose that the interface ComponentResources be extended with a method to allow such access.
--
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] Assigned: (TAPESTRY-2610) Allow access to component's
informal parameters
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-2610:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Allow access to component's informal parameters
> -----------------------------------------------
>
> Key: TAPESTRY-2610
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2610
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.14
> Reporter: Kalin Krustev
> Assignee: Howard M. Lewis Ship
>
> A component may need to access all its parameters, including informal ones. This is for example when the component needs to process arbitrary list of parameters as needed when accessing a database with a query. I propose that the interface ComponentResources be extended with a method to allow such access.
--
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] Commented: (TAPESTRY-2610) Allow access to component's
informal parameters
Posted by "Tobias Wehrum (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625290#action_12625290 ]
Tobias Wehrum commented on TAPESTRY-2610:
-----------------------------------------
I second this request... without the nasty workaround by using InternalComponentResourcesImpl.getInformalParameterBindings(), this would be a blocker for one of my components. Adding this method to the interface would be great.
> Allow access to component's informal parameters
> -----------------------------------------------
>
> Key: TAPESTRY-2610
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2610
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.14
> Reporter: Kalin Krustev
>
> A component may need to access all its parameters, including informal ones. This is for example when the component needs to process arbitrary list of parameters as needed when accessing a database with a query. I propose that the interface ComponentResources be extended with a method to allow such access.
--
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