EObject
is the root of all modeled objects so all the method names start with "e" to distinguish the EMF methods from the client methods. It provides support for the behaviors and features common to all modeled objects:
EObject
is assumed to also implement {@link InternalEObject}, which provides lower-level access that is not necessarily suitable for general consumption but is required for maintaining the EMF support mechanisms. Implementations of EObject should extend {@link org.eclipse.emf.ecore.impl.BasicEObjectImpl BasicEObjectImpl} or one of its derived classes because methods can and will be added to this API. The framework also assumes that implementations will not specialize {@link #equals(Object)} (nor {@link #hashCode()}) so that "==
" can be always used for equality testing; {@link org.eclipse.emf.ecore.util.EcoreUtil#equals(EObject,EObject) EcoreUtil.equals} should be used for doing structural equality testing.
@extends Notifier
@see org.eclipse.emf.ecore.EcorePackage#getEObject()
@model
@generated
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|