[ve-dev] Re: cartoon images of widgets...ComponentManagerProxy not resol

["Namrata" <namrata@xxxxxxxxxxxxxx>]

Hi Rich,

Thanks to your inputs, I now have a very clear understanding of the
infrastructure.

I have started my implementation and am stuck at a point for past 2 days -

The 'fComponentManagerBeanProxy' in 'ComponentManager' is returning as
proxyNotResolved. However my visual proxy is getting resolved appropriately.

I suspect that I have to setup some configuration item so that the Registry
knows the location of the jar file, that defines
"org.eclipse.ve.internal.jfc.vm.ComponentManager".

Here is a truncated portion of my code -

protected void instantiateAndInitialize(IExpression expression){
                ....
                IProxy bProxy = InstantiateBeanProxy(expression,

(IElement)target);
                / * bProxy is an expression Proxy. It will be resolved after
invokeExpression */

                 getComponentManager().setComponentBeanProxy(bProxy,
                                              expression,
getModelChangeController() );

                 try{
                           expression.invokeExpression();
                  }
                ....
 }

This is causing an exception in
org.eclipse.ve.internal.jfc.core.ComponentManager.getRegistry(ComponentManag
er.java:781)

Am I missing something in configuring the registry? Or is there something
wrong in the flow of my code?
I understand that I have to pass an unresolved beanProxy along with the
expression to the ComponentManager.
Is that correct, or do I have to pass a resolved beanProxy?

Thanks
Namrata
----------------------------------------------------------------------------
-----------------------------------------------------
>
> Hi,
>
> The ComponentManager exists on both sides. There is an IDE version that
> you talk to, and there is a ComponentManager on the vm side that the IDE
> ComponentManager talks to. You need one on the vm side so that it can
> listen to the actual component and signal back when it changes size or
> location and when it needs to be re-layed out. The ComponentManager on the
> vm side is the fComponentManagerBeanProxy.
>
> Rich