blocks|key|135263|text|Java提供了注入机制，使我们的对象能够获得对资源和其他依赖项的引用，而不必直接实例化它们(显式地使用‘new’关键字)。我们只需在类中声明所需的资源&类中的其他依赖项，方法就是使用注解来绘制字段或方法，注解表示编译器的注入点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|135264|然后，容器在运行时提供所需的实例。注入的优点是它简化了我们的代码，并将其与其依赖项的实现解耦。|135265|这两种方法都有助于实现控制反转。|135266|Take+a+look+at+one+of+my+article+I+wrote+on+this.|offset|length|135267|entityMap|0|LINK|mutability|MUTABLE|url|http://java.dzone.com/articles/resource-injection-vs^0|0|0|0|0|1D|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Java EE provides injection mechanisms that enable our objects to obtain the references to resources and other dependencies without having to instantiate them directly (explicitly with ‘new’ keyword). We simply declare the needed resources &amp; other dependencies in our classes by drawing fields or methods with annotations that denotes the injection point to the compiler.

The container then provides the required instances at runtime. The advantage of Injection is that it simplifies our code and decouples it from the implementations of its dependencies.

Both the methods facilitates in achieving Inversion Of Control.

<a href="http://java.dzone.com/articles/resource-injection-vs" rel="noreferrer">Take a look at one of my article I wrote on this.</a>

blocks|key|134196|text|从source|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|134197|JNDI资源注入使您能够将|134198|名称空间中可用的任何资源注入到任何容器管理的对象中，例如servlet、企业bean或托管bean。例如，我们可以使用资源注入来注入数据源、连接器或JNDI命名空间中可用的任何其他所需资源。|blockquote|134199|134200|Java+使我们能够将常规的类转换为托管对象，并将它们注入任何其他托管对象(由容器管理的对象)。|style|BOLD|134201|资源注入和依赖注入之间的差异+RI和DI之间的差异如下所示。|134202|134203|JNDI资源注入可以直接注入JNDI资源，而依赖注入cannot.|134204|Dependency注入可以直接注入常规类(受管|unordered-list-item|134205|
|134206|)，而资源注入通过资源名称解析，而依赖注入通过type.|134207|134208|Dependency注入解析是类型安全的，而资源注入不是类型安全的。|134209|134210|entityMap|0|LINK|mutability|MUTABLE|url|http://java.dzone.com/articles/resource-injection-vs^0|1|6|0|0|0|0|0|E|Y|0|0|U|0|0|0|X|0|0|O|0|0|0|S|0|0|0|Y|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]]|C|$]]|$1|D|3|E|5|6|7|1F|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1G|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|1I|8|@$A|1J|B|1K|L|M]]|9|@]|C|$]]|$1|N|3|O|5|6|7|1L|8|@$A|1M|B|1N|L|M]]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1P|8|@$A|1Q|B|1R|L|M]]|9|@]|C|$]]|$1|S|3|T|5|U|7|1S|8|@$A|1T|B|1U|L|M]]|9|@]|C|$]]|$1|V|3|W|5|6|7|1V|8|@]|9|@]|C|$]]|$1|X|3|Y|5|U|7|1W|8|@$A|1X|B|1Y|L|M]]|9|@]|C|$]]|$1|Z|3|W|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|10|3|11|5|U|7|20|8|@$A|21|B|22|L|M]]|9|@]|C|$]]|$1|12|3|-4|5|6|7|23|8|@]|9|@]|C|$]]|$1|13|3|-4|5|6|7|24|8|@]|9|@]|C|$]]]|14|$15|$5|16|17|18|C|$19|1A]]]]

From the <a href="http://java.dzone.com/articles/resource-injection-vs" rel="noreferrer">source</a>:

<blockquote>
 Resource injection enables you to inject any resource available in the
 JNDI namespace into any container-managed object, such as a servlet,
 an enterprise bean, or a managed bean. For eg, we can use resource
 injection to inject data sources, connectors, or any other desired
 resources available in the JNDI namespace.
 
 Dependency injection enables us to turn regular Java classes into
 managed objects and to inject them into any other managed object
 (objects wich are managed by the container).
 
 Difference between Resource Injection and Dependency Injection The
 differences between the RI and DI are listed below.
 
 <ol>
 <li>Resource Injection can inject JNDI Resources directly whereas Dependency Injection cannot.</li>
 <li>Dependency Injection can inject Regular Classes (managed bean) directly whereas Resource Injection cannot.</li>
 <li>Resource Injection resolves by resource name whereas Dependency Injectin resolves by type.</li>
 <li>Dependency Injection is typesafe whereas Resoiurce Injection is not.</li>
 </ol>
</blockquote>

blocks|key|2915443|text|看看这个：Java+EE+Injection|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2915444|Main+differences+between+resource+injection+and+DI：|2915445|📷|atomic|2915446|​|2915447|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.oracle.com/javaee/7/tutorial/injection.htm|1|https://docs.oracle.com/javaee/7/tutorial/injection003.htm|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6e439f90e3c9899a7fee629acd471d10.png|imageAlt^0|5|H|0|0|0|1E|1|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|F|3|G|5|H|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|I|3|J|5|6|7|1C|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]|U|$5|V|O|W|C|$X|Y|Z|-4]]]]

Check this out: <a href="https://docs.oracle.com/javaee/7/tutorial/injection.htm" rel="noreferrer">Java EE Injection</a>

<a href="https://docs.oracle.com/javaee/7/tutorial/injection003.htm" rel="noreferrer">Main differences between resource injection and DI</a>:
<a href="https://i.stack.imgur.com/78Ydm.png" rel="noreferrer"><img src="https://i.stack.imgur.com/78Ydm.png" alt="Difference between resource injection and "></a>

blocks|key|134233|text|Rahul+Tripathi的答案是准确和正确的。但是，为了更简洁地帮助您决定使用哪个接口，让我们这样看待它:+DI通常用于将实现类分配给接口。而RI用于从JNDI提取属性值和JDBC连接。DI允许您针对接口编写代码，并在以后决定使用哪个实现。通常，当RI对象不仅仅是属性值时，以及DI用于传递属性值时，会有一些重叠。正如我已经提到的，JDBC连接就是这种重叠的一个很好的例子。JDBC连接不仅是一个连接字符串(属性值)，也是一个实现(使用哪些驱动程序)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|134234|我认为如果你正在使用DI，并且你需要传递一些属性值，那就继续使用DI。如果你正在使用RI并且需要传递一个对象，那么如果可能的话，只需要在RI中传递即可。最终，如果两者都使用，那么需要填写的XML文件就会更多。|134235|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Rahul Tripathi answer is exact and the correct one. But to put it in more succinct way that can help you decide which to use lets look at it this way: DI is typically used to assign implementation classes to interfaces. Whereas RI is used to extract property values, and JDBC connections from JNDI. DI allows you to write code against interfaces and decide later on which implementation to use. There is some overlap, typically when the RI'd objects are more than just a property value and when the DI is used to pass a property value. A good example of this overlap, as I already mentioned, is JDBC connections. A JDBC connection is not only a connection string (property values) it is also an implementation (which drivers to use).

I think if you are using DI and you need to pass some property value, just continue using DI. And if you are using RI and need to pass an object, than just do it in RI if possible. Ultimately if you use both, then that's more XML files that need to be filled out.

I have been learning Java EE for while and found Java EE provides two types of injection mechanisms 

<ol>
<li>Resource Injection </li>
<li>Dependency Injection</li>
</ol>

Please guide me to understand the difference between Resource Injection &amp; Dependency Injection.

What is difference between resource injection and dependency injection (CDI) in Java?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我一直在学习Java EE，我发现Java EE提供了两种类型的注入机制资源注入依赖项注入请指导我理解资源注入和依赖注入之间的区别。

问Java中的资源注入和依赖注入(CDI)有什么不同？
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java中的资源注入和依赖注入(CDI)有什么不同？EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java中的资源注入和依赖注入(CDI)有什么不同？
EN