[
https://issues.apache.org/jira/browse/TAPESTRY-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555158
]
Howard M. Lewis Ship commented on TAPESTRY-2005:
------------------------------------------------
I do believe this to be a bug.
A simple work-around would be to define an interface, in a non-controlled
package, and use that for the parameter type (and be sure the passed parameter
is assignable to the interface type).
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
