The NoSuchMethodError is an indicator of a
binary compatibility problem. Changing the return type like you’ve
described maintains source compatibility, but breaks binary compatibility.
- Konstantin
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason A Sholl
Sent: Monday, May 15, 2006 12:20
PM
To: General
discussion of project-wide or architectural issues.
Cc: [email protected];
[EMAIL PROTECTED]
Subject: Re: [wtp-dev]
java.lang.NoSuchMethodError:org.eclipse.wst.common.frameworks.datamodel.IDataModel.getDefaultOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation;
I did change this back in March, but am not sure why
this is broken. The change was to return an IDataModelPausibleOperation
instead of IDataModelOperation,
however, IDataModelPausibleOperation
extends IDataModelOperation..
Why would that cause breakage?
Thank you,
Jason A. Sholl
[EMAIL PROTECTED]
919-543-0011 (t/l 441-0011)
|
Arthur Ryman
<[EMAIL PROTECTED]>
Sent
by: [EMAIL PROTECTED]
05/15/2006 03:07 PM
|
Please
respond to
"General discussion of project-wide or
architectural issues." <[email protected]>
|
|
|
To
|
[email protected]
|
|
cc
|
|
|
Subject
|
[wtp-dev]
java.lang.NoSuchMethodError:
org.eclipse.wst.common.frameworks.datamodel.IDataModel.getDefaultOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation;
|
|
Did someone delete a method from this interface? This was reported at Geronimo.
I opened a bug to track it [1]
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=141850
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
|
