x




java version "1.2.2"
Classic VM (build JDK-1.2.2-001, native threads, symcjit)

Am I mad, or doesn't the PropertyEditorSupport(Object) constructor need to be
public for delegation to work?

The fact that this bug has not been reported before now is a testament to the
fact that noone uses PropertyEditorSupport via delegation from another class.
(not even the QA people who should have tested this functionality)
(Review ID: 99727) 
======================================================================

Create a sub-class of PropertyEditorSupport that provides a public constructor
for delegation. But that defeats the whole purpose doesn't it?
======================================================================

This is a valid point. One of the desires of some of the builder vendors is to expose the source component of a PropertyEditor. 

We should also add get/setSource() as well. Ideally, we should add these methods /requirements on PropertyEditor but that is an interface and we would be breaking a lot of existing code.
  xxxxx@xxxxx   2001-12-10

Some licensees have been requesting that we introduce a new interface to get the source object. We may consider that option but in the meantime, we can get the same functionality by exposing the source object in PropertyEditorSupport.

They also advise that the specification should emphasise that the source object should be for informational purposes only (read only).

  xxxxx@xxxxx   2003-03-17