|
|||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||
See:
Description
| Interface Summary | |
| IFlexibleProject | Represents a project that supports a flexible project model. |
| IVirtualComponent | Represents a component as defined by the .wtpmodules file. |
| IVirtualContainer | Represents a component as defined by the WTP Modules file. |
| IVirtualFile | Represents a file that can be navigated through an abstract ("virtual") path. |
| IVirtualFolder | Represents a folder that can be navigated through an abstract ("virtual") path. |
| IVirtualReference | Represents a dependency between two components: EnclosingComponent->ReferencedComponent. |
| IVirtualResource | Allows clients to work with flexible project structures using API similar to the Eclipse Platform IResource model. |
| Class Summary | |
| ComponentHandle | Provides a handle to a component within a project. |
The ComponentCore Virtual Path API allows clients to navigate logical collections of files within Eclipse projects using API similar to the Eclipse IResource API.
| Virtual Path API |
|
The Virtual Path API provides a facade to the flexible project model. Each IVirtualResource represents a resource from the runtime component under a virtual runtime path. Each IVirtualResource may represent one or more Eclipse Platfrom resources located at the same runtime path. |
|
Each IVirtualResource is contained by exactly one IVirtualComponent. However, the underlying resources that are represented by the IVirtualResource may be contained by multiple IVirtualComponents. IVirtualComponents are contained by IFlexibleProjects. Each IFlexibleProject may contain one or more IVirtualComponents. |
|
|
|
Figure 1: A visual representation of a possible mapping between a Virtual structure and a Platform Resource structure. |
|
|
|
Figure 2: Virtual Path Model |
|
|||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||