You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: posts/2025-09-23-25.0.0.10-beta.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta
82
82
[#overrideLibrary]
83
83
== OverrideLibrary support for application classloader
84
84
85
-
The 25.0.0.10-beta release introduces a new type of library reference for configuring an application’s `<classloader/>`that can be used to configure an the override library reference. The override library reference is similar to a private library reference because class instances remain unique to the application’s classloader. The key difference is the search order. With an override library reference, the library class path is searched before the application’s own class path, this allows the library path to override classes that are already included in the application.
85
+
The 25.0.0.10-beta release introduces a new type of library reference for configuring an application’s `<classloader/>`that can be used to configure an the override library reference. The override library reference is similar to a private library reference because class instances remain unique to the application’s classloader. The key difference is the search order. With an override library reference, the library class path is searched before the application’s own class path, this allows the library path to override classes that are already included in the application.
86
86
87
87
For example, suppose a `<webApplication/>` contains a class such as `org.acme.needs.fix.SomeImpl` that must be overridden to resolve an issue. If rebuilding the application to include the fix is difficult or undesirable, you can instead build a new library JAR (for example, someImplFix.jar) with the corrected class files. The following `server.xml` configuration shows how to use an `overrideLibraryRef` to apply the fix without rebuilding the application:
0 commit comments