Description Darin Wright 2001-10-10 22:50:56 EDT

DW (5/24/00 10:13:57 AM)
	The JDOM APIs claim that DOMException is only thrown in programming 
error cases (i.e.
	an illegal manipulation has been attempted). This is no longer true, 
since it can now
	be thrown when trying to get the detailed contents for a node. We 
should enhance the
	exception to have a status code, and add to our APIs letting the client 
know where
	it can really be thrown.

DW (5/24/00 11:02:01 AM)
	Update generic comment for DOMException itself, . Post-beta
	we may have to own up to all the places an exception can be thrown 
(with a checked
	exception).

DW (5/25/00 10:57:46 AM)
	Made Doc change for beta.

DW (6/15/00 10:44:02 AM)
	Migrate DOMException to be a "checked" exception - i.e. a subclass of 
Exception.

	The DOMException should have a status code (similar to 
JavaModelException and CoreException).
	The exception should indicate which node caused the problem.
	An interface should define the possible codes:

		SYNTAX_ERROR - this code means that detailed source indexes for 
the node could not be
			determined, and thus the request could not be completed 
(i.e. setting or getting the
			requested attribute).
		CYCLE_ERROR - this code means that adding a child or inserting 
a sibling would cause a cycle
			in the document fragment graph
		ILLEGAL_NODE_TYPE - the element being added/inserted is of an 
illegal type - for example,
			a package statement cannot be added as a child of a 
member
		NODE_ALREADY_PARENTED - this means a node being added as a 
child is already parented.

	Estimate: 1 day