You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Nick Westgate (JIRA)" <de...@tapestry.apache.org> on 2007/08/08 12:56:59 UTC
[jira] Created: (TAPESTRY-1696) Event handlers should treat List
like the "special
Event handlers should treat List like the "special
--------------------------------------------------
Key: TAPESTRY-1696
URL: https://issues.apache.org/jira/browse/TAPESTRY-1696
Project: Tapestry
Issue Type: Improvement
Reporter: Nick Westgate
--
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] Updated: (TAPESTRY-1696) Event handlers should be able to
receive all parameters as a List (rather than only as Object[])
Posted by "Nick Westgate (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Westgate updated TAPESTRY-1696:
------------------------------------
Comment: was deleted
> Event handlers should be able to receive all parameters as a List (rather than only as Object[])
> ------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1696
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1696
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Nick Westgate
>
> A context can be passed to a component as a List, but an event handler must currently use Object[] instead.
> For example, the following handler will receive all context parameters:
> void onEventFromComponent(Object[] things) { ... }
> But this next handler will receive a List containing only the first parameter:
> void onEventFromComponent(List things) { ... }
> This happens because Object[] is explicitly coded as "special" in OnEventWorker.java, buildMethodParameters().
> It would be nice to accord List the same "special" status.
> Cheers,
> Nick.
--
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] Updated: (TAPESTRY-1696) Event handlers should be able to
receive all parameters as a List (rather than only as Object[])
Posted by "Nick Westgate (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Westgate updated TAPESTRY-1696:
------------------------------------
Component/s: tapestry-core
Description:
A context can be passed to a component as a List, but an event handler must currently use Object[] instead.
For example, the following handler will receive all context parameters:
void onEventFromComponent(Object[] things) { ... }
But this next handler will receive a List containing only the first parameter:
void onEventFromComponent(List things) { ... }
This happens because Object[] is explicitly coded as "special" in OnEventWorker.java, buildMethodParameters().
It would be nice to accord List the same "special" status.
Cheers,
Nick.
Affects Version/s: 5.0.5
Summary: Event handlers should be able to receive all parameters as a List (rather than only as Object[]) (was: Event handlers should treat List like the "special)
Oops, hit return.
> Event handlers should be able to receive all parameters as a List (rather than only as Object[])
> ------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1696
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1696
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Nick Westgate
>
> A context can be passed to a component as a List, but an event handler must currently use Object[] instead.
> For example, the following handler will receive all context parameters:
> void onEventFromComponent(Object[] things) { ... }
> But this next handler will receive a List containing only the first parameter:
> void onEventFromComponent(List things) { ... }
> This happens because Object[] is explicitly coded as "special" in OnEventWorker.java, buildMethodParameters().
> It would be nice to accord List the same "special" status.
> Cheers,
> Nick.
--
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-1696) Event handlers should be able to
receive all parameters as a List (rather than only as Object[])
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1696.
------------------------------------------
Resolution: Duplicate
Assignee: Howard M. Lewis Ship
Duplicate of TAPESTRY-1999 (or vice-versa).
> Event handlers should be able to receive all parameters as a List (rather than only as Object[])
> ------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1696
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1696
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Nick Westgate
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> A context can be passed to a component as a List, but an event handler must currently use Object[] instead.
> For example, the following handler will receive all context parameters:
> void onEventFromComponent(Object[] things) { ... }
> But this next handler will receive a List containing only the first parameter:
> void onEventFromComponent(List things) { ... }
> This happens because Object[] is explicitly coded as "special" in OnEventWorker.java, buildMethodParameters().
> It would be nice to accord List the same "special" status.
> Cheers,
> Nick.
--
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] Updated: (TAPESTRY-1696) Event handlers should be able to
receive all parameters as a List (rather than only as Object[])
Posted by "Nick Westgate (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Westgate updated TAPESTRY-1696:
------------------------------------
Priority: Minor (was: Major)
> Event handlers should be able to receive all parameters as a List (rather than only as Object[])
> ------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1696
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1696
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Nick Westgate
> Priority: Minor
>
> A context can be passed to a component as a List, but an event handler must currently use Object[] instead.
> For example, the following handler will receive all context parameters:
> void onEventFromComponent(Object[] things) { ... }
> But this next handler will receive a List containing only the first parameter:
> void onEventFromComponent(List things) { ... }
> This happens because Object[] is explicitly coded as "special" in OnEventWorker.java, buildMethodParameters().
> It would be nice to accord List the same "special" status.
> Cheers,
> Nick.
--
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