<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>CDI on Pal Hargitai Personal Blog</title>
    <link>https://palhargitai.eu/tags/CDI/</link>
    <description>Recent content in CDI on Pal Hargitai Personal Blog</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 05 Jan 2014 14:33:45 +0000</lastBuildDate>
    <atom:link href="https://palhargitai.eu/tags/CDI/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Good and Bad of CDI</title>
      <link>https://palhargitai.eu/post/2014-01-05-the-good-and-bad-of-cdi/</link>
      <pubDate>Sun, 05 Jan 2014 14:33:45 +0000</pubDate>
      <guid>https://palhargitai.eu/post/2014-01-05-the-good-and-bad-of-cdi/</guid>
      <description>&lt;h1&gt;A little background&lt;/h1&gt;
CDI has had a major influence in the Java community. It&#39;s inclusion into JEE6 has greatly improved the way of working with JEE in general, this itself caused a major leap in adoption of JEE. So far so, that it&#39;s being applied indiscriminately, something I&#39;m not much of a fan of. For most of the web applications being built, CDI is a great tool to accelerate implementation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
