Tigerstripe Project Dependencies

Because Service Contracts are meant to interact within a complete SOA Solution, very often they will share common information models. To avoid duplication and increased complexity, such commonalities between Tigerstripe projects can be saved into a Tigerstripe Module. The module can further be referenced by other projects. These referenced Tigerstripe Modules are called Project Dependencies.

Project Dependencies

Project Dependencies are a list of referenced Tigerstripe Modules required for a Tigerstripe Project. These dependencies typically contain common information models, for example a common definition of a Customer Entity, so that all Service Contracts of an end-to-end solution are based on common definitions.

Dependencies can be added to and removed from the list of dependencies of a project through the Dependencies Tab of the Tigerstripe Descriptor Editor as show below:

Note: If a project dependency cannot be satisfied (for example a missing file), the project will likely not be valid.

Tigerstripe Modules

Project Dependencies are references to a set of Tigerstripe Modules, for example, pre-packaged, binary-like, versions of Tigerstripe projects. Refer to Import/Export Tasks for more details on how to export an existing Tigerstripe Project into a module that can be referenced as a dependency by other projects.

Although Tigerstripe modules have a .jar file extension, they contain additional Tigerstripe specific information to further identify the content of a module. This additional information is displayed when selecting a referenced dependency in a Tigerstripe project descriptor (as show in the above image):

Related Topics

Source Model
Project Descriptor


© copyright 2005, 2006, 2007 Cisco Systems, Inc. - All rights reserved