Error retrieiving type manager for multi-level VOBs

An incorrect VOB path is used to retrieve the type manager in Base ClearCase environments that reuse an existing snapshot view whose load rules are configured to process a subdirectory of a VOB. The error generated is:

2010-05-06 10:01:36,209 WARN  [btpool0-114] fisheye.app ClearCaseContext-handleProcessError - Error executing command (cleartool lstype -l eltype:text_file@/vob/insight/insightgui ) :  cleartool: Error: Unable to determine VOB for pathname "/vob/insight/insightgui".

This problem only occurs when the FishEye repository is configured to reuse an existing snapshot view, and the load rules for the snapshot view include a VOB subpath reference (eg. /vob/insight/insightgui) instead of the actual VOB location (eg. /vob/insight).

FishEye is assuming that the path specified in the load rule is the VOB location, and uses this value when it tries to perform an operation to find the type manager for a file type.