SOAPFaultNode defines methods conflicting with DOM
--------------------------------------------------
Key: AXIOM-363
URL: https://issues.apache.org/jira/browse/AXIOM-363
Project: Axiom
Issue Type: Bug
Components: API
Affects Versions: 1.2.11
Reporter: Andreas Veithen
Priority: Minor
Fix For: 1.3
The Axiom API is designed in such a way that an implementation can support both
Axiom and DOM. If a method defined by an Axiom interface has the same signature
as a method defined by the corresponding DOM interface, then these methods must
have the same contract. E.g. the OMElement#getLocalName() method has the same
behavior as org.w3c.dom.Node#getLocalName() (when invoked on an Element
instance), so that a class may implement both OMElement and Element.
There is one exception to this rule. SOAPFaultNode defines the following
methods:
void setNodeValue(String uri);
String getNodeValue();
These methods are in conflict with methods defined by org.w3c.dom.Node. Since
SOAPFaultNode is specific to SOAP 1.2, renaming these two methods has limited
impact. We should do this for Axiom 1.3.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
