Hi Stephan,
> I'd prefer to stick with UnknownPropertyException here, for the reasons
> you already stated: UnknownPropertyException is already used in
> combination with attributes, namely to model optional attributes.
(is it? I did not find any such interface.)
Then we perhaps should think about re-using the
XPropertyChangeListener/PropertyChangeEvent, too, and just introduce a new
interface XAttributeChangeBroadcaster
{
addPropertyChangeListener( [in] XPropertyChangeListener );
removePropertyChangeListener( [in] XPropertyChangeListener );
};
(the methods cannot be named *AttributeChangeListener, since I seem to
remember that some generic reflection services do not accept them as
valid listener concepts then - they only accept
"add/removeFooListener(XFooListener)", but not
"add/removeFooListener(XBarListener)".)
Carrying this further, we could rename XAttributeChangeBroadcaster to
XPropertyChangeBroadcaster and simply define that it might be used for
broadcasting attribute changes, too ....
> (Besides, my current understanding of how exception mechanisms for
> programming environments should be designed tells me that the "checked"
> com.sun.star.beans.UnknownPropertyException and its use at
> com.sun.star.beans.XPropertySet.addPropertyChangeListener is a mistake.
> Hence, we should not make the situation worse by introducing a
> "checked" UnknownAttributeException as the next mistake).
What do you mean with "checked" here (Sorry if this question reveales my
ignorance :)
> Turns out I did not look very thoroughly at your initial posting...
Ts ts. :)
Ciao
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
