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 2008/01/24 11:41:35 UTC
[jira] Updated: (TAPESTRY-2079) Component class type is lost when
it is passed outside Tapestry application pages or components package
[ https://issues.apache.org/jira/browse/TAPESTRY-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Priit Karu updated TAPESTRY-2079:
---------------------------------
Attachment: example.ZIP
Attached Maven2 example project that illustrates the problem.
Just in case my wording was too confusing...
> Component class type is lost when it is passed outside Tapestry application pages or components package
> -------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2079
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2079
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 5.0
> Reporter: Priit Karu
> Attachments: example.ZIP
>
>
> I obtain component container inside one component (e.g. call ComponentResources.getContainer()) and when i check the class type inside the same component method everything is ok but when i decide to pass the same component to an utility class that do the same there it fails.
> E.g. i have two methods inside my component class and the first one returns true, the second one false although the code should be the same for both (only different package/class):
> public boolean isInsideTestContainerLocally(){
> Component comp = resources.getContainer();
> return (comp instanceof TestContainer);
> }
>
> public boolean isInsideTestContainerWithCall(){
> Component comp = resources.getContainer();
> return Util.isInstanceOfTestContainer(comp);
> }
> ----->>----Util class contains the method---->----
> public static boolean isInstanceOfTestContainer(Component _comp){
> return _comp instanceof TestContainer;
> }
--
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