Surprisingly, what ends up happening is that definstances of A have a
slot named b with an initial value of type
external_address/java.beans.PropertyDescriptor. This may actually the
the same bug as an unsolved one reported by Glenn Williams. What's happening is
that the Rete.assert() function, on seeing the null value, is assuming
that the slot should be initialized to the default value. It doesn't
understand that defclasses use the data structures differently than do
deftemplates, so that's how the PropertyDescriptor ends up in
there. This actually has a number of implications; as soon as I come
up with a neat patch I will publish it here. Thanks for the report.
I think S.S. OZSARIYILDIZ wrote:
>
>
> >
> > A question : My beans have some properties which are as default contains
> > null value. Because of this jess does not show the property names. Is
> > three a way to get rid of this problem still with null values.
> >
>
> An example (edited)
>
> class A
> {
> protected B myB = null;
>
> public B getB( )
> {
> return myB;
> }
>
> // prop listeners ect...
> }
>
>
> Note that myB is an optional property and it is not constructed.
> When I construct it or instanced it there is no problem
---------------------------------------------------------
Ernest Friedman-Hill
Distributed Systems Research Phone: (925) 294-2154
Sandia National Labs FAX: (925) 294-2234
Org. 8920, MS 9214 [EMAIL PROTECTED]
PO Box 969 http://herzberg.ca.sandia.gov
Livermore, CA 94550
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list. List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
