WAS v8.5 > Administering applications and their environment > Administering the Liberty profile > Administering the Liberty profile manually > Configure class loaders and libraries for Java EE applications
Removing access to third-party APIs for a Java EE application
By default, Java™ EE applications do not have access to the third-party APIs available in the Liberty profile. We can also configure this state explicitly in server.xml, or an included file. In the following example, an application called Painter has previously been configured to access third-party APIs, as described in Accessing third-party APIs from a Java EE application. You want to remove this access, and to make it explicit in the configuration that the application now uses the default access setting.
The application also uses a common library called Haarlem. This library is in the ${server.config.dir}/lib/Haarlem directory.
- Configure class loading for the application, to show that the application can no longer access the third-party APIs.
In server.xml, or an included file, remove third-party from the set of values included for the apiTypeVisibility attribute:
<application id="painter" name="Painter" type="ear" location="painter.ear"> <classloader apiTypeVisibility="spec, ibm-api" commonLibraryRef="Haarlem" /> </application>- Optional: If the application uses any common libraries, set those libraries to use the same API type visibility setting.
In server.xml, or an included file, add the following code:
<library id="Haarlem" apiTypeVisibility="spec, ibm-api"> <fileset dir="${server.config.dir}/lib/Haarlem" includes="*.jar" scanInterval="5s" /> </library>
Parent topic: Configure class loaders and libraries for Java EE applications
Related
Using a Java library with a Java EE application
Sharing a library across multiple Java EE applications
Providing global libraries for all Java EE applications
Accessing third-party APIs from a Java EE application
Overriding a provided API with an alternative version
|