modules/enterprise/server/jar/intentional-api-changes-since-4.9.0.xml | 8 ++++++++
1 file changed, 8 insertions(+)
New commits:
commit 56c6467abcfe9af7e61568209a55267a48a4a5be
Author: Jirka Kremser <jkremser(a)redhat.com>
Date: Mon Sep 30 17:19:40 2013 +0200
api checks: adding the change as a intentional change not to break JON compatibility.
diff --git a/modules/enterprise/server/jar/intentional-api-changes-since-4.9.0.xml
b/modules/enterprise/server/jar/intentional-api-changes-since-4.9.0.xml
index 488adc3..6ab00ba 100644
--- a/modules/enterprise/server/jar/intentional-api-changes-since-4.9.0.xml
+++ b/modules/enterprise/server/jar/intentional-api-changes-since-4.9.0.xml
@@ -56,4 +56,12 @@
<justification>Adding a method to a remote API interface is safe. This is
method is added in order to deprecate the getAggregate. For more details see the previous
intentional change.</justification>
</difference>
+ <difference>
+
<className>org/rhq/enterprise/server/operation/OperationManagerRemote</className>
+ <differenceType>7006</differenceType> <!-- method return type changed
-->
+ <method>org.rhq.core.domain.util.PageList
findOperationDefinitionsByCriteria(org.rhq.core.domain.auth.Subject,
org.rhq.core.domain.criteria.OperationDefinitionCriteria)</method>
+ <to>java.util.List</to>
+ <justification> While this is technically a welcome change (because impl of
that method returned the PageList anyway), it breaks the strongly typed clients, because
the methods are linked by their full signature and hence a library compiled against
JON312GA version of that remote will fail to find the method with the new signature and
will fail with NoSuchMethodError at runtime.</justification>
+ </difference>
+
</differences>
Show replies by date