This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/openwebbeans-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 171ba5f Automatic Site Publish by Buildbot
171ba5f is described below
commit 171ba5f339979bf1979c26b1c1e1f87af43e3895
Author: buildbot <[email protected]>
AuthorDate: Fri May 8 11:10:41 2026 +0000
Automatic Site Publish by Buildbot
---
output/cdi_explained.html | 1 +
1 file changed, 1 insertion(+)
diff --git a/output/cdi_explained.html b/output/cdi_explained.html
index d9c1421..2cb08c1 100644
--- a/output/cdi_explained.html
+++ b/output/cdi_explained.html
@@ -98,6 +98,7 @@ JSR-299 (CDI-1.0), JSR-346 (CDI-1.1/1.2) and JSR-365
(CDI-2.0).
Apache OpenWebBeans implements these standards. This page will give you an
introduction to features of
CDI in general. We will add a special hint whenever a feature is ambiguous in
the specification
and OpenWebBeans implements it in a certain way which might be different on
other CDI containers.</p>
+<p>From CDI-4.0 onwards, we did move from the <code>javax</code> to the
<code>jakarta</code> package space.</p>
<h2 id="what-is-cdi-at-all">What is CDI at all?<a class="headerlink"
href="#what-is-cdi-at-all" title="Permalink">¶</a></h2>
<p>Originally developed under the name ‘Web Beans’, the CDI
specification was created
to fill the gaps which could not be filled by Enterprise Java Beans (EJB) on
the back end,
