> exception UnknownAttributeException: com::sun::star::uno::Exception
Given that there is a UnknownPropertyException, I wonder whether it
should be reused. I misses the property name, but might in theory
already be used to indicate that an attribute is optional. (At least I
saw code which suggests this in the PropertySetMixing implementation,
though I didn't find such an attribute.)
If we'd introduce UnknownAttributeException and allow it at
setters/getters, e.g.
interface XFoo
{
[attribute] string Bar
{
set raises (UnknownAttributeException);
set raises (UnknownAttributeException);
};
};
then at least places as the PropertySetMixin implementation need to be
adjusted.
Personally, I'd prefer having an UnknownAttributeException over re-using
UnknownPropertyException, for clarity reasons. Other opinions?
Thanks & Ciao
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
