W3C home > Mailing lists > Public > www-di@w3.org > June 2005

DPF Section 4.2.4 missing exceptions

From: Keith Waters <kwaters@ftrd.us>
Date: Thu, 2 Jun 2005 08:38:21 -0400
Message-Id: <5D5BFF1E-DE67-438D-AFE5-082D22273988@ftrd.us>
To: www-di@w3.org

Hi Jeremy,

This message contains a response to comments on

http://www.w3.org/TR/2004/WD-DPF-20041122/

e8:
section 4.2.4
last sentence misses cases

Are there not four cases which can raise a
NO_MODIFICATIONS_ALLOWED_ERR?
    newChild is read only
    oldChild is read only
    this property is read only
    the previous parent of oldChild is read only
the text only identifies two of these.


The DPF Working Group agrees, and have been working through the  
document to address exceptions more comprehensively.
With respect to the particular Interface 4.2.4 replaceDPFFProperty is  
is now 5.1.2.3 replaceDPFProperty and is defined as follows:

DPFProperty replaceDPFProperty(in DPFProperty newChild,
                                in DPFProperty oldChild)
             raises(DPFException);

     This method is used to replace an existing child property with a  
new child property. The new child's parent data item is set to this  
property. If it was previously the child of another property, it will  
be automatically removed from that property before being added to  
this one.

     Parameters

         newChild

             The new child property that will replace an old child  
property.
         oldChild

             The old child property that will be replaced by a new  
child property.

     Return Value
         DPFProperty The return value is the property being replaced.  
The return value is the new child property that replaced the old  
child property. If an error occured during the operation, the value  
NULL is returned.

     Exceptions

         DPFException

             NO_MODIFICATIONS_ALLOWED_ERR: This exception is raised  
if the current parent property under which a child property is being  
replaced is read only and cannot be modified.

             HIERARCHY_REQUEST_ERR: This exception is raised if the  
child property that replaces the old property do not belong to the  
property type supported by the parent, if the child property is an  
ancestor of the current parent property or a replica of the current  
parent property itself.

             NOT_FOUND_ERR: This exception is raised if the old child  
that is being replaced by the new child is not a child of the current  
parent property.

             TYPE_MISMATCH_ERR: This exception is raised when there  
is a DPF object type mismatch between the parent, new child and old  
child being replaced. For example, adding a DPFPropertyList when a  
DPFProperty is expected.

-Keith Waters
Received on Thursday, 2 June 2005 13:40:43 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 2 June 2005 13:40:44 GMT