Bug 221337 [Markers] MarkerItem has too much API
We are exposing too much as API in MarkerItem. We should only provide getAtttributeValue and the methods that support PATH_ATTRIBUTE and NAME_ATTRIBUTE as they are tricky. Everything else needs to be pushed down to an internal class. We should mention the relevant IMarker constants for those removed.
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkerCategory.java
.getMarkerLimit()),
							String.valueOf(getChildrenCount()) });
		}
		if (size == 1)
			return NLS.bind(MarkerMessages.Category_One_Item_Label,
					new Object[] { name });
		return NLS.bind(MarkerMessages.Category_Label, new Object[] { name,
				String.valueOf(size) });
	}
	/* (non-Javadoc)
	 * @see org.eclipse.ui.views.markers.MarkerItem#getChildrenCount()
	 */
	public int getChildrenCount() {
		return end - start + 1;
	}
	/*
	 * (non-Javadoc)
	 * 
	 * @see org.eclipse.ui.views.markers.internal.MarkerNode#isConcrete()
	 */
	public boolean isConcrete() {
		return false;
	}
	/*
	 * (non-Javadoc)
	 * 
	 * @see org.eclipse.ui.views.markers.internal.MarkerNode#getConcreteRepresentative()
	 */
	public MarkerEntry getConcreteRepresentative() {
		return cachedMarkerBuilder.getMarkerEntries()[start];