[英]Should I package my app into wildfly/jboss modules? (or any Java EE server equivalent tek)
I have taken over a large EE app which was mostly deployed as wildfly/jboss modules. 我已经接管了一个大型的EE应用程序,该应用程序主要是作为wildfly / jboss模块部署的。 There are separate apps off-course, and then there are this large number of modules. 路线外有单独的应用程序,然后有大量的模块。
Now, I get it - the intent is to share these components between multiple apps deployed on your server. 现在,我明白了-目的是在服务器上部署的多个应用程序之间共享这些组件。 But this also tightly couples these modules and to all of these apps. 但这也将这些模块与所有这些应用紧密结合在一起。 Also, Wildfly/JBoss has the facility to load dependencies from other modules, and each deployment is a module. 另外,Wildfly / JBoss具有从其他模块加载依赖项的功能,并且每个部署都是一个模块。 Why should I package anything into the wildfly/modules/system/layers/base directory? 为什么要将任何内容打包到wildfly / modules / system / layers / base目录中? Why not just deploy wars and ears as wildfly/standalone/deployments and define inter-module depdencies there? 为什么不只是将战争和耳朵部署为“野蝇” /“独立” /“部署”并在那里定义模块间依赖关系呢?
What is the best practice? 最佳做法是什么? What am I missing here? 我在这里想念什么?
Deploying code in my own deployments allows it to be shared between multiple other deployments and allows for hot deployment. 在我自己的部署中部署代码可以使其在多个其他部署之间共享,并允许热部署。
It is never a good idea place your code within the wildfly system modules. 将您的代码放在wildfly系统模块中绝不是一个好主意。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.