RE: [ve-dev] About beans

[Rich Kulp <richkulp@xxxxxxxxxx>]

Janek,

That means ULFillerBeanInfo is not being
found. Are you sure ULCFillerBeanInfo.getProperties() is being called?
Because if it is calling ULCFillerBeanInfo.getProperties(), then it must
call ULCFillerBeanInfo.getAdditional (though actually it is calling IvjBeanInfo.getAdditional
since ULCFillerBeanInfo is not overriding it). 

Please step into the Introspector constructor
when doing ULCFiller. Make sure that it is finding ULCFillerBeanInfo as
the "explicitBeanInfo" and that it is calling getAdditional in
there. That is where it does the call to getAdditional.

Rich

"Janak Mulani" <janak.mulani@xxxxxxxxx>
Sent by: ve-dev-admin@xxxxxxxxxxx

10/29/2004 12:44 PM

Please respond to
ve-dev

To	<ve-dev@xxxxxxxxxxx>
cc
Subject	RE: [ve-dev] About beans

Rich,
 
I debugged it with breakpoints
in IvjBeanInfo.getAdditional:
 
The thing is that for ULCFiller
the Introspector does not call getAdditional method at all, it calls that
method for its super.
(ULCComponent). I fail to understabd
why.
 
However for ULCLabel getAdditional
method is called and the subsequent call to override.
 
Does this piece of info help in
any way?
 
Thanks,
 
Janak
-----Original Message-----
From: ve-dev-admin@xxxxxxxxxxx [mailto:ve-dev-admin@xxxxxxxxxxx]On
Behalf Of Rich Kulp
Sent: Friday, October 29, 2004 6:22 PM
To: ve-dev@xxxxxxxxxxx
Subject: RE: [ve-dev] About beans


Janek, 

There is only one way from the code you given me that the over call would
not be made, and that is if in IvjBeanInfo.getAdditionalBeanInfo() this
failed and threw an exception: 

                BeanInfo[] result
= new BeanInfo[] { 
                    
   Introspector.getBeanInfo(getBeanClass().getSuperclass())
                };


Rich