You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Kyle Marvin (JIRA)" <be...@incubator.apache.org> on 2005/04/08 18:37:24 UTC

[jira] Assigned: (BEEHIVE-508) Control id related issue

     [ http://issues.apache.org/jira/browse/BEEHIVE-508?page=history ]

Kyle Marvin reassigned BEEHIVE-508:
-----------------------------------

    Assign To: Kyle Marvin

> Control id related issue
> ------------------------
>
>          Key: BEEHIVE-508
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-508
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1, V1Alpha, V1Beta
>  Environment: Win2k , x86
>     Reporter: Mridul Muralidharan
>     Assignee: Kyle Marvin
>     Priority: Critical

>
> This is my mail to the alias.
> I will try to attach a testcase soon - but the idea of the bug is explained below.
> --
> Hi all,
>  I am observing some problems with control id's that get returned by the ControlBean.getControlID().
> I will try to explain what I am trying :
>  I have a nested control within another control's impl like this :
> @ControlImplementation
> public class SomeControlAImpl implements SomeControlA , Serializable{
>  @Control
>  SomeControlB controlB;
>  .... // proper initialization of SomeControlAImplClientInitializer is done.
> }
> Within SomeControlB , when I invoke "context.getControlHandle().getControlID();" - it gives the proper path based id "instance/controlB".
> Now , when this gets serialized and then deserialized , a lookup on for this bean succeeds (using : container.getBean(controlId)) , but the getControlID() on this bean instance which is returned gives me the id as "controlB" not "instance/controlB".
> Because of this , event firing using control handle , etc fails.
> After some digging , I suspect that is it 'cos of what is mentioned in "ControlBean.setControlID" -> "// TODO: The ID change needs to be propagated down to nested children".
> Is this the case ? or am I missing something else here ?
> And if it is indeed the case , then is this going to be fixed for beehive 1.0 release ?
> Thanks and Regards,
> Mridul 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira