Definitely sounds like a bug and one that should be fixed by 1.0
release. Please open a high priority JIRA issue and mark it as such,
and I'll take a look!
-- Kyle
On Apr 8, 2005 11:19 AM, Mridul Muralidharan
<[EMAIL PROTECTED]> wrote:
> 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
>
