Jar依赖项 - 应用程序服务器类路径vs将其添加到应用程序war本身 [英] Jar dependency - Application server classpath vs adding it to the application war itself

问题描述

我们安装了Weblogic 10.3.6。
在其上运行的应用程序需要以下jar

We have an installation of Weblogic 10.3.6. An application running on it needs the following jar

com.oracle.ws.http_client_1.3.0.0.jar

上面的jar位于服务器包Oracle\Middleware \modules \ com.oracle中.ws.http_client_1.3.0.0.jar

The above jar is located in the server bundle Oracle\Middleware\modules\com.oracle.ws.http_client_1.3.0.0.jar

什么是正确的方法？
这个jar（看起来是由Oracle编写的系统库，在mvnrepository网站上找不到）应该添加到服务器类路径中还是应该将它添加到应用程序存档（war）？谢谢。

What's the right approach? Should this jar (appears to be a system library written by Oracle, not found on mvnrepository site) be added to the server classpath or should I add it to the application archive (war)?? Thanks.

更新：上面的jar也捆绑了Weblogic（默认情况下没有添加到classpath），在maven public repo中找不到。那么，这不是要直接添加到应用程序中吗？

Update: Also the above jar comes bundled with Weblogic (not added to classpath by default though) and is not found in maven public repo. So, this is not meant to be added to the application directly?

推荐答案

1. 如果jar是应用程序服务器环境/构建的一部分我不会将它添加到war / ear文件中。它应该可以通过所有env DIT / UAT / PROD（envs需要与prod一致）。此外，当应用应用程序serever修复程序或服务器升级时，我们将使用最新的jar。

1. If the jar is part of the application server environment/build I would not add it to the war/ear file. It should be availble through out all the env DIT/UAT/PROD (envs need to be consistent with prod). Also when the app serever fixes are applied or server is upgaded we will be using the lastest jar.

在其他情况下（外部），最好打包它在战争中是为了避免在从env迁移到env时出现问题。

In other cases(external) it would be best to package it in war in order to avoid issues while migrating from env to env.

这篇关于Jar依赖项 - 应用程序服务器类路径vs将其添加到应用程序war本身的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！