Colin Chalmers wrote: > > Hi John, > > We noticed the problem you mention below (two setters first one found is > used (not always correct one)) in the 2.2 src from a couple of weeks ago. > Could you (pretty please?) confirm your fix is in the latest 2.2 src? This > would help resolve a workaround I had to implement for a colleague which > meant having the method in question public whilst the others were protected > (if I remember it correctly). >
The changes are in cvs as of Oct 21. Are you experiencing the same behavior as before? The code in PropertyDescriptor, that is being used now, appears correct and I have been running with the fulcrum version with no problems. BeanInfo contained the bug and it is no longer being used. john mcnally -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
