You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Priit Karu (JIRA)" <de...@tapestry.apache.org> on 2007/12/31 13:20:43 UTC
[jira] Updated: (TAPESTRY-2005) Using component classes as
component parameters fails (Could not find a coercion)
[ https://issues.apache.org/jira/browse/TAPESTRY-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Priit Karu updated TAPESTRY-2005:
---------------------------------
Attachment: simpleExample.ZIP
Attached simple maven2 example project to reproduce the problem (bug?)
> Using component classes as component parameters fails (Could not find a coercion)
> ---------------------------------------------------------------------------------
>
> Key: TAPESTRY-2005
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2005
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.7
> Reporter: Priit Karu
> Attachments: simpleExample.ZIP
>
>
> We need to use inside one Tapestry component a parameter which value type is another component class (in the example bug.components.TestComponent). When binding this parameter it fails with an error message: "Could not find a coercion from type bug.components.TestComponent to type bug.components.TestComponent.".
> It seems that at runtime the component classes do not match (some bytecode manipulation probably).
> Are we doing something incorrectly or it is not allowed to define parameters which type is some other component class?
--
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