You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2011/04/11 20:56:05 UTC
[jira] [Created] (AXIOM-363) SOAPFaultNode defines methods
conflicting with DOM
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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Commented] (AXIOM-363) SOAPFaultNode defines methods
conflicting with DOM
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118996#comment-13118996 ]
Hudson commented on AXIOM-363:
------------------------------
Integrated in ws-axiom-trunk #580 (See [https://builds.apache.org/job/ws-axiom-trunk/580/])
AXIOM-363: Deprecated the getNodeValue/setNodeValue methods in SOAPFaultNode (and added replacement methods) because they conflict with DOM methods and will be removed in Axiom 1.3.
AXIOM-363: Automatically check for collisions between the Axiom API and DOM.
veithen :
Files :
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/util/CopyUtils.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/soap/SOAPFaultNode.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/apache/axiom/soap/SOAPFaultNodeTestBase.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-dom/src/main/java/org/apache/axiom/soap/impl/dom/SOAPFaultNodeImpl.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/soap/impl/llom/SOAPFaultNodeImpl.java
veithen :
Files :
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/apache/axiom/om/DOMCompatibilityTest.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/apache/axiom/om/MethodCollisionTestCase.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/apache/axiom/om/MethodSignature.java
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/test/java/org/apache/axiom/soap/DOMCompatibilityTest.java
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org