本文整理汇总了Java中org.eclipse.emf.ecore.InternalEObject.eDirectResource方法的典型用法代码示例。如果您正苦于以下问题：Java InternalEObject.eDirectResource方法的具体用法？Java InternalEObject.eDirectResource怎么用？Java InternalEObject.eDirectResource使用的例子？那么恭喜您, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类org.eclipse.emf.ecore.InternalEObject的用法示例。
在下文中一共展示了InternalEObject.eDirectResource方法的1个代码示例，这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞，您的评价将有助于系统推荐出更棒的Java代码示例。
示例1: defaultGetURIFragment
import org.eclipse.emf.ecore.InternalEObject; //导入方法依赖的package包/类
/**
* We don't use a {@link IFragmentProvider} here. The implementation is a complete copied from
* {@link ResourceImpl#getURIFragment}
*
* @param eObject
* the object the URI fragment should be calculated for.
* @return the calculated URI fragment
*/
private String defaultGetURIFragment(EObject eObject) {
// Copied from ResourceImpl.getURIFragment to avoid the caching
// mechanism which will add a content
// adapter which in turn will resolve / load the resource (while the
// purpose of all the code is to
// avoid resource loading)
InternalEObject internalEObject = (InternalEObject) eObject;
if (internalEObject.eDirectResource() == this || unloadingContents != null
&& unloadingContents.contains(internalEObject)) {
return "/" + getURIFragmentRootSegment(eObject);
} else {
SegmentSequence.Builder builder = SegmentSequence.newBuilder("/");
boolean isContained = false;
for (InternalEObject container = internalEObject
.eInternalContainer(); container != null; container = internalEObject
.eInternalContainer()) {
builder.append(container.eURIFragmentSegment(internalEObject.eContainingFeature(), internalEObject));
internalEObject = container;
if (container.eDirectResource() == this || unloadingContents != null
&& unloadingContents.contains(container)) {
isContained = true;
break;
}
}
if (!isContained) {
return "/-1";
}
builder.append(getURIFragmentRootSegment(internalEObject));
builder.append("");
builder.reverse();
// This comment also resides in ResourceImpl.getURIFragment:
// Note that we convert it to a segment sequence because the
// most common use case is that callers of this method will call
// URI.appendFragment.
// By creating the segment sequence here, we ensure that it's
// found in the cache.
//
return builder.toSegmentSequence().toString();
}
}