WAS v8.5 > Administer applications and their environment > Administer the Liberty profile > Administer the Liberty profile using WebSphere Studio > Define a utility project as a shared library

Setting a web project to use shared libraries

If we have a utility project defined as a shared library, we can associate defined shared libraries with a web project.

A shared library is an external Java™ archive (JAR) file used by one or more applications. Using shared libraries enables multiple application published on a server to use a single library, rather than use multiple copies of the same library. After you associate shared libraries with an application or project, the application or module class loader loads classes in the shared libraries and make those classes available to the application or module.

  1. To set a web project to use shared libraries:

    1. In the Project Explorer view, right-click the web project to associate shared libraries.
    2. Select Properties > Liberty Profile Shared Libraries.
    3. In the IDs field, specify one or more shared library identifiers you want the project to reference. To specify multiple identifiers, use a comma-separated list. For example: ID1, ID2, ID3

      The shared library identifier is the value specified in the Shared Libary ID field from the Define a utility project as a shared library task.

  2. You might want to add its associating utility projects to the class path for compilation-purpose:

    1. In the Project Explorer view, right-click your project that you are associating shared libraries.
    2. Select Properties > Java Build Path.
    3. Select the Projects tab.

    4. Click Add.
    5. Select the utility projects the project references.

  3. Develop the artifacts in the web project. For example, we can add a servlet in a web project that references classes in the shared libraries.

  4. Add the web project to the server. For more details see Add and running an application on the Liberty profile using WebSphere Studio topic.


Results

Here is an example entry added to the server configuration (server.xml) file:


Parent topic: Define a utility project as a shared library


Related


Configure class loaders and libraries for Java EE applications
Sharing a library across multiple Java EE applications
Overriding a provided API with an alternative version


|