tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <...@tapestry.apache.org>
Subject [jira] Assigned: (TAPESTRY-2005) Using component classes as component parameters fails (Could not find a coercion)
Date Tue, 01 Jan 2008 00:11:46 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship reassigned TAPESTRY-2005:
----------------------------------------------

    Assignee: Howard M. Lewis Ship

> 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
>            Assignee: Howard M. Lewis Ship
>         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


Mime
View raw message