diff --git a/news/page/12.html b/news/page/12.html
index c8d00031..e694be8a 100644
--- a/news/page/12.html
+++ b/news/page/12.html
@@ -141,6 +141,307 @@
+
+
+
+ 2016-10-25
+
+
+
+ tips
+
+
+
+ Martin Kouba
+
+
+
+
+
+
In this article we’re going to dive into various performance aspects of CDI applications.
+ As you’ve probably noticed performance testing is sometimes tricky.
+ First of all, it’s difficult to create a meaningful benchmark.
+ One should understand the JVM specifics (the need for warmup, garbage collection, JVM settings, etc.) and also use appropriate tools (e.g. JMH for microbenchmarks) accordingly.
+ But even that usually proves to be unsufficient.
+ One should also run the test in a relevant context (data, load, etc.).
+ Performance specialists also say that’s it’s good to avoid premature optimizations but keep performance aspects in mind when tuning the "final" code.
+ But all these considerations are out of scope of this article.
+ Let’s go through several areas where CDI affects the performance of your application and discuss the possibilities.
+
+
+
Bootstrap
+
+
+
During bootstrap the overhead of a framework should be minimal so that it does not slow down the application startup and also does not eat all the memory available.
+ However, CDI needs to do all that magic behind the scenes - read annotations, build and validate metadata, etc.
+ The following sections describe what could be done to minimize the impact.
+
+
+
Discovery mode
+
+
In CDI 1.0 there was only one "discovery mode".
+ How does it work?
+ Simply put: find all bean archives (containing beans.xml), discover and process all the found classes (identify beans, etc.).
+ Needless to say, this might be a performance problem for large applications with thousands of classes.
+ In CDI 1.1+ we call this mode all and a bean archive with this mode is called EXPLICIT.
+ Since CDI 1.1+ a new discovery mode - annotated - can be used.
+ The difference is that if this mode is used only classes with a bean defining annotation are considered.
+ In other words, a component must be explicitly designated.
+ A bean archive with this mode is called IMPLICIT.
+ To make things a little bit more complicated, an implicit bean archive does not have to contain a beans.xml file at all.
+ One class with a bean defining annotation or a session bean is enough.
+
+
+
Implicit bean archive has pros and cons:
+
+
+
+ -
+
saves a lot of memory if an archive contains a lot of classes which should NOT become beans (the container does not have to store the metadata)
+
+ -
+
speeds up the bootstrap (the container does not have to process all the types, fire events like ProcessBean, etc.)
+
+ -
+
does not fire ProcessAnnotatedType for all types from the bean archive; this breaks some extensions (e.g. MessageBundleExtension from DeltaSpike)
+
+ -
+
does not pick up @javax.inject.Singleton beans (it’s not a bean defining annotation)
+
+
+
+
+
CONCLUSION: If possible, use the annotated discovery mode.
+
+
+
+
+ |
+
+ |
+
+ Most Weld-based runtimes allow to suppress implicit bean archives without beans.xml, i.e. to require the beans.xml file in bean archives so that it’s not necessary to scan all the parts of the application. See also FAQ.
+ |
+
+
+
+
+
+
+
Extensions
+
+
CDI portable extensions are essential integration points.
+ And users love integrated technologies.
+ However, the more extensions the more work must be done during bootstrap.
+ For example, there is a ProcessAnnotatedType container lifecycle event.
+ This event is fired:
+
+
+
+ -
+
for every type in an EXPLICIT bean archive,
+
+ -
+
for every session bean and every type with a bean defining annotation in an IMPLICIT bean archive.
+
+
+
+
+
The delivery might be restricted by means of type arguments, e.g. for observer void observeNumbers(@Observes ProcessAnnotatedType<? extends Number> event) an extension will be notified for every class assignable to Number.
+ However, if you do <T> void observe(@Observes ProcessAnnotatedType<T> event) your extension will be notified for every class that is discovered.
+ Now if we have an application with one EXPLICIT bean archive with 2000 classes, then a specific observer method on such extesion will be called 2000x.
+ And if there are three similar extensions, the CDI container will have to create 2000 events and notify 6000 observers.
+ This should be ok unless the observer logic is overly complex.
+
+
+
+
+
+ |
+
+ |
+
+ If possible, don’t use the extensions which observe all the annotated types from your application, i.e. which defined something like void observe(@Observes ProcessAnnotatedType<?> event).
+ Since CDI 1.1 @WithAnnotations should be used to restrict the set of types an extension is going to process. Weld Probe warns you about these extensions.
+ |
+
+
+
+
+
+
Jandex
+
+
In some environments (WildFly, Weld SE, and more) Weld can leverage an "offline reflection library", such as Jandex, to speed up the scanning process.
+ These libraries allow to effectively filter classes which are not beans and vetoed classes.
+ It works like this: Jandex generates an index (scans the bytecode) and Weld is using this index to filter out useless classes.
+ As a result Weld does not even have to _load the classes or use reflection API to detect types which should be ignored.
+
+
+
+
+ |
+
+ |
+
+ In Weld SE and Servlet it’s also possible to generate the Jandex index beforehand, e.g. using the Ant task.
+ |
+
+
+
+
+
+
+
+
Runtime
+
+
+
In runtime the overhead of a framework should be minimal so that it’s not an application bottleneck.
+ However, CDI needs to do all that magic behind the scenes - create bean instances, manage contexts, intercept and decorate invocations, etc.
+ The following sections describe what could be done to minimize the impact.
+
+
+
Identify problematic components easily
+
+
Before you start a profiler or a similar tool, it’s a good idea to identify all the CDI components involved in a problematic "request".
+ This means all the beans, observer methods, interceptors and decorators.
+ The good start might be the Weld Probe invocation trees view.
+ An invocation tree shows all the business method invocations (including producers, disposers and observer methods).
+ Once you spot a problematic component, you can check the business logic and associated interceptors and decorators.
+ Sometimes profilers are just an overkill.
+
+
+
+
Lazy initialization of bean instances
+
+
Weld initializes bean instances of normal scoped beans lazily.
+ In other words, when injecting a normal scoped bean (@RequestScoped, @ApplicationScoped, etc.) a new instance is not created until actually used.
+ Instead, a shared client proxy is injected.
+ This proxy invokes a method upon the correct bean instance (created if necessary).
+
+
+
+
+ |
+
+ |
+
+ Having many injection points resolving to normal scoped beans does not necessarily mean additional overhead associated with bean instance creation.
+ |
+
+
+
+
+
In the following example, an OrderProcessor instance is not created until its OrderProcess.process() method is called:
+
+
+
+
@ApplicationScoped
class OrderProcessor {
@PostConstruct
void init() {
// Do some expensive initialization logic
}
void process() {
// Business logic
}
}
@RequestScoped
class OrderService {
@Inject
OrderProcessor processor; // A shared client proxy is injected
void create(Order order) {
if (order.isValid()) {
// Processor is not initialized unless we have a valid order
processor.process(order);
}
}
}
+
+
+
+
+
+ |
+
+ |
+
+ Weld’s session context is also initilized lazily and doesn’t require an HTTP session to actually exist until a bean instance must be written (i.e. until a method of a @SessionScoped bean is invoked).
+ |
+
+
+
+
+
+
Drawbacks of @Dependent pseudo-scope
+
+
From performance point of view @Dependent is NOT a best fit for:
+
+
+
+ -
+
a bean that declares a producer which is frequently used (i.e. the produced bean is created very often)
+
+ -
+
a bean that declares an observer method which is frequently notified (i.e. the event is fired very often)
+
+ -
+
a bean which is used in EL expressions
+
+
+
+
+
For all these cases, a new @Dependent bean instance is created to handle the logic and destroyed when the invocation/evaluation completes.
+ In other words, the bean instances are not reused.
+ That’s not necessarily a problem if a bean does not have an "expensive" initialization or depends on others "heavyweight" components.
+ But very often, a wider scope is more suitable.
+
+
+
+
Mapping CDI contexts to HTTP requests
+
+
By default, bult-in CDI contexts are activated at the beginning of an HTTP request processing and deactivated once the processing finishes.
+ This might be an unnecessary overhead in certain situations, e.g. when serving static resources (images, JavaScript, etc.).
+ Weld allows to activate the contexts only for a subset of requests only.
+ A regular expression may be used for filtering HTTP requests that should have contexts active during their processing.
+
+
+
+
<web-app version="3.1" xmlns="http://xmlns.jcp.org/xml/ns/javaee/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
<context-param>
<param-name>org.jboss.weld.context.mapping</param-name>
<param-value>.*\.html</param-value> <!-- Only activate contexts for resources with html suffix, e.g. /some/path.html -->
</context-param>
</web-app>
+
+
+
+
+
Bean identifier index optimization
+
+
This optimization is used to reduce the HTTP session replication overhead (clustering use case).
+ Simply put: Weld tries to minimize the amount of bytes send over the network.
+ However, the inconsistency detection mechanism may cause problems in environments where application stop does not imply HTTP session destruction.
+ Thus it’s disabled by default in Servlet containers.
+ See also the reference guide for more info.
+
+
+
+
+
+
+
-
-
- 2014-4-15
-
-
- Jozef Hartinger
-
-
-
-
-
-
CDI 1.2
-
-
-
CDI 1.2 is a maintenance release of the CDI specification. It contains a number of small fixes and clarifications as well as several enhancements.
- Most notable changes for application developers are related to the definition of bean defining annotations.
-
-
-
In CDI 1.2, the set of bean defining annotations now contains:
-
-
-
- -
-
all the normal scope annotations (e.g. @RequestScoped, @ApplicationScoped, …)
-
- -
-
the built-in @Dependent scope
-
- -
-
@Interceptor and @Decorator annotations
-
- -
-
stereotype annotations
-
-
-
-
-
As a result, any class annotated with a bean defining annotation is by default recognized by the application server and registered as a CDI bean. The beans.xml file is optional.
-
-
-
In addition, there are other fixes, clarifications and minor enhancements in this maintenance release of the CDI specification.
- See the release notes for the complete list of changes.
-
-
-
-
-
-
-
-
Weld is now capable of using bytecode-scanning utilities, such as the Jandex tool, to speed up deployment.
- This is especially notable in extra large deployments (e.g. 5000+ classes) where we observed up to 20% faster deployment.
-
-
-
In addition, there are noticeable improvements in the following areas:
-
-
-
- -
-
runtime performance of observers, interceptors and decorators
-
- -
-
session replication overhead (failover)
-
- -
-
memory consumption
-
-
-
-
-
-
-
Weld 2.2 on WildFly
-
-
-
WildFly does not come with Weld 2.2 support yet. It is however easy to patch an existing WildFly installation to use Weld 2.2.
-
-
-
To do so, follow these steps:
-
-
-
- -
-
Download a patch appropriate for the WildFly version (e.g. 8.0.0.Final) from the download section
-
- -
-
In the WildFly installation, run the CLI console
-
-
- -
-
From the console run the following command:
-
-
-
patch apply /path/to/wildfly-8.0.0.Final-weld-2.2.0.Final-patch.zip
-
-
-
-
-
-
Your installation is now patched!
-
-
-
-
-
Weld SE and Servlet
-
-
-
Weld comes with the SE module which allows CDI to be used in plain Java SE environment. In Weld 2.2 we added partial support for implicit bean archives.
- Partial support here means that the beans.xml file is still required, but bean-discovery-mode=”annotated” can be specified for Weld to only discover classes explicitly annotated with bean defining annotations (see above).
-
-
-
In addition to the Weld SE module, Weld also provides the Weld Servlet module which makes it possible to use Weld on top of a plain Servlet container, such as Apache Tomcat or Jetty.
-
-
-
In this release we simplified configuration by bootstrapping Weld using the ServletContainerInitializer.
-
-
-
Furthermore, Weld Servlet now supports Jetty 9.1. At the same time, the support for Tomcat 6 was dropped. To summarize, Weld Servlet is currently supported on the following Servlet containers:
-
-
-
- -
-
Tomcat 7, 8
-
- -
-
Jetty 7, 8, 9.0, 9.1
-
-
-
-
-
-
-
Acknowledgement
-
-
-
We greatly appreciate your contributions to this release.
- Big thanks go to: Martin Kouba, Matúš Abaffy, Matej Briškár, Ron Šmeral, Marek Schmidt, Marko Lukša, Tomáš Remeš, Stuart Douglas, Radoslav Husár, Max Pimm, Alexandre Gattiker, Antonin Stefanutti and Steve Moyer.
-
-
-
-
-
-
-
diff --git a/news/page/18.html b/news/page/18.html
index 4e90b2ad..55be1121 100644
--- a/news/page/18.html
+++ b/news/page/18.html
@@ -141,6 +141,165 @@
+
+
+
+ 2014-4-15
+
+
+ Jozef Hartinger
+
+
+
+
+
+
CDI 1.2
+
+
+
CDI 1.2 is a maintenance release of the CDI specification. It contains a number of small fixes and clarifications as well as several enhancements.
+ Most notable changes for application developers are related to the definition of bean defining annotations.
+
+
+
In CDI 1.2, the set of bean defining annotations now contains:
+
+
+
+ -
+
all the normal scope annotations (e.g. @RequestScoped, @ApplicationScoped, …)
+
+ -
+
the built-in @Dependent scope
+
+ -
+
@Interceptor and @Decorator annotations
+
+ -
+
stereotype annotations
+
+
+
+
+
As a result, any class annotated with a bean defining annotation is by default recognized by the application server and registered as a CDI bean. The beans.xml file is optional.
+
+
+
In addition, there are other fixes, clarifications and minor enhancements in this maintenance release of the CDI specification.
+ See the release notes for the complete list of changes.
+
+
+
+
+
+
+
+
Weld is now capable of using bytecode-scanning utilities, such as the Jandex tool, to speed up deployment.
+ This is especially notable in extra large deployments (e.g. 5000+ classes) where we observed up to 20% faster deployment.
+
+
+
In addition, there are noticeable improvements in the following areas:
+
+
+
+ -
+
runtime performance of observers, interceptors and decorators
+
+ -
+
session replication overhead (failover)
+
+ -
+
memory consumption
+
+
+
+
+
+
+
Weld 2.2 on WildFly
+
+
+
WildFly does not come with Weld 2.2 support yet. It is however easy to patch an existing WildFly installation to use Weld 2.2.
+
+
+
To do so, follow these steps:
+
+
+
+ -
+
Download a patch appropriate for the WildFly version (e.g. 8.0.0.Final) from the download section
+
+ -
+
In the WildFly installation, run the CLI console
+
+
+ -
+
From the console run the following command:
+
+
+
patch apply /path/to/wildfly-8.0.0.Final-weld-2.2.0.Final-patch.zip
+
+
+
+
+
+
Your installation is now patched!
+
+
+
+
+
Weld SE and Servlet
+
+
+
Weld comes with the SE module which allows CDI to be used in plain Java SE environment. In Weld 2.2 we added partial support for implicit bean archives.
+ Partial support here means that the beans.xml file is still required, but bean-discovery-mode=”annotated” can be specified for Weld to only discover classes explicitly annotated with bean defining annotations (see above).
+
+
+
In addition to the Weld SE module, Weld also provides the Weld Servlet module which makes it possible to use Weld on top of a plain Servlet container, such as Apache Tomcat or Jetty.
+
+
+
In this release we simplified configuration by bootstrapping Weld using the ServletContainerInitializer.
+
+
+
Furthermore, Weld Servlet now supports Jetty 9.1. At the same time, the support for Tomcat 6 was dropped. To summarize, Weld Servlet is currently supported on the following Servlet containers:
+
+
+
+ -
+
Tomcat 7, 8
+
+ -
+
Jetty 7, 8, 9.0, 9.1
+
+
+
+
+
+
+
Acknowledgement
+
+
+
We greatly appreciate your contributions to this release.
+ Big thanks go to: Martin Kouba, Matúš Abaffy, Matej Briškár, Ron Šmeral, Marek Schmidt, Marko Lukša, Tomáš Remeš, Stuart Douglas, Radoslav Husár, Max Pimm, Alexandre Gattiker, Antonin Stefanutti and Steve Moyer.
+
+
+
+
+
+
+
-
-
- 2013-9-20
-
-
- Martin Kouba
-
-
-
-
-
A tip how to configure a new feature introduced in Weld 2.1.0.Beta2 which allows to skip CDI context activation for some HTTP requests: http://goo.gl/PAiwBS
-
-
-
-
diff --git a/news/page/19.html b/news/page/19.html
index 49ea0283..139a2648 100644
--- a/news/page/19.html
+++ b/news/page/19.html
@@ -141,6 +141,24 @@
+
+
+
+ 2013-9-20
+
+
+ Martin Kouba
+
+
+
+
+
A tip how to configure a new feature introduced in Weld 2.1.0.Beta2 which allows to skip CDI context activation for some HTTP requests: http://goo.gl/PAiwBS
+
+
+
+
Weld has a new web site!
diff --git a/news/page/2.html b/news/page/2.html
index 0ac2aa0a..8ce78356 100644
--- a/news/page/2.html
+++ b/news/page/2.html
@@ -141,6 +141,120 @@
+
+
+
+ 2023-10-26
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Looking for a CDI 4.1 implementation? We’ve got you covered!
+ Weld Core 6.0.0.Alpha1 is now available and comes along with CDI API 4.1.0.Alpha1.
+ Note that this version also uses latest version (2.2.0-RC1) of the Jakarta Interceptors specification.
+
+
+
CDI/CDI TCK related additions:
+
+
+
+ -
+
Create first implementation of CDI method invokers using MethodHandles (WELD-2764)
+
+
+ -
+
If you want to read up more about the original CDI API design and PR, take a look (here)
+
+ -
+
Note that this feature is still being improved on both, CDI side and (Weld side) but the general shape of it is already carved out
+
+
+
+ -
+
Support standardized means of getting interceptor bindings from InvocationContext (WELD-2756)
+
+
+ -
+
This was already possible via set of methods in WeldInvocationContext as well as the String key under which we stored these bindings in InvocationContext
+
+ -
+
Both of the above are no deprecated (but still working) and users are expected to use the standardized approach
+
+
+
+ -
+
Support inspectable CreationalContext and Contextual in CDI TCK SPI (WELD-2757)
+
+
+
+
+
Other bugfixes and project QoL features:
+
+
+
+ -
+
Fix proxy creation for beans using @Typed and having package-protected types split across packages (WELD-2758)
+
+ -
+
Correct how we determine proxy package for beans with unassignable types in their bean type set (WELD-2763)
+
+
+ -
+
WeldManager#getContexts now correctly returns an empty set when there are no contexts for given scope (WELD-2761)
+
+ -
+
Fix possible memory leak with repetitive thread group creation (WELD-2755)
+
+ -
+
WeldInitialListener can no longer throw NPE is application fails to start (WELD-2752)
+
+
+ -
+
LazySessionBeanStore no longer swallows exceptions happening when attempting to initiate HTTP session (WELD-2762)
+
+ -
+
Weld Core and Weld API are now using formatter plugin and impsort instead of checkstyle (WELD-2753)
+
+ -
+
Jandex version was bumped to 3.x across the project (WELD-2754)
+
+
+
+
+
As always, if you find further issues with Weld 6, let us know and we’ll try to help.
+
+
+
+
+
-
-
-
- 2022-10-3
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Weld Core 5.1.0.Final and Weld API 5.0.SP3 are now availabe in Maven Central.
-
-
-
Most notable change, which is also the cause of a minor version bump, is the removal of Weld Probe from our codebase.
- Details are in this JIRA issue and were also communicated via weld-dev email.
-
-
-
In short, Probe hasn’t been maintained for a long time and its UI part is using outdated libraries and would need to be completely re-written which is something that we opted not to do at the moment.
- The JIRA issue has more information as to how we could re-integrate it in the future if there is interest from the community.
-
-
-
-
- |
- Warning
- |
-
- Probe removal affects any integrators that were using Probe up until now! This typically concerns EE integrators such as WildFly or Liberty.
- |
-
-
-
-
-
As usual, here is a list of notable bugfixes in this version:
-
-
-
- -
-
Made decorators more Groovy friendly (WELD-2713)
-
- -
-
Updated Jandex and remove deprecated usages (WELD-2724)
-
- -
-
Added tools to execute TCK lang model in EE container (using WildFly) (WELD-2725)
-
- -
-
Introduced method to WeldManager which allows to obtain instances of all registered contexts regardless of whether they are active (WELD-2726)
-
- -
-
Brought WildFly Arquillian dependency setup up to date and fix affected examples (WELD-2727)
-
- -
-
AbstractResourceServices in Weld API now correctly take into consideration lookup value of @Resource (WELD-2728)
-
- -
-
AbstractResourceServices now supports setter methods for @Resource where the name is defaulted (WELD-2732)
-
- -
-
Corrected the implementation of WeldExpressionFactory#equals (WELD-2729)
-
- -
-
Fixed BeanManager bean types to also include BeanContainer (WELD-2731)
-
- -
-
Avoid logging information about non-bindings member when using BeanManager#isQualifier for annotations that aren’t qualifiers (WELD-2643)
-
- -
-
Removal of Weld Probe (WELD-2733)
-
-
-
-
-
-
-
diff --git a/news/page/3.html b/news/page/3.html
index 7ea1a698..5aa0f314 100644
--- a/news/page/3.html
+++ b/news/page/3.html
@@ -141,6 +141,94 @@
+
+
+
+ 2022-10-3
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Weld Core 5.1.0.Final and Weld API 5.0.SP3 are now availabe in Maven Central.
+
+
+
Most notable change, which is also the cause of a minor version bump, is the removal of Weld Probe from our codebase.
+ Details are in this JIRA issue and were also communicated via weld-dev email.
+
+
+
In short, Probe hasn’t been maintained for a long time and its UI part is using outdated libraries and would need to be completely re-written which is something that we opted not to do at the moment.
+ The JIRA issue has more information as to how we could re-integrate it in the future if there is interest from the community.
+
+
+
+
+ |
+ Warning
+ |
+
+ Probe removal affects any integrators that were using Probe up until now! This typically concerns EE integrators such as WildFly or Liberty.
+ |
+
+
+
+
+
As usual, here is a list of notable bugfixes in this version:
+
+
+
+ -
+
Made decorators more Groovy friendly (WELD-2713)
+
+ -
+
Updated Jandex and remove deprecated usages (WELD-2724)
+
+ -
+
Added tools to execute TCK lang model in EE container (using WildFly) (WELD-2725)
+
+ -
+
Introduced method to WeldManager which allows to obtain instances of all registered contexts regardless of whether they are active (WELD-2726)
+
+ -
+
Brought WildFly Arquillian dependency setup up to date and fix affected examples (WELD-2727)
+
+ -
+
AbstractResourceServices in Weld API now correctly take into consideration lookup value of @Resource (WELD-2728)
+
+ -
+
AbstractResourceServices now supports setter methods for @Resource where the name is defaulted (WELD-2732)
+
+ -
+
Corrected the implementation of WeldExpressionFactory#equals (WELD-2729)
+
+ -
+
Fixed BeanManager bean types to also include BeanContainer (WELD-2731)
+
+ -
+
Avoid logging information about non-bindings member when using BeanManager#isQualifier for annotations that aren’t qualifiers (WELD-2643)
+
+ -
+
Removal of Weld Probe (WELD-2733)
+
+
+
+
+
+
+
-
-
-
- 2022-3-23
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Final ballot of CDI 4 has uncovered untested and unimplemented area in the newly added Startup and Shutdown events.
-
-
-
Our previous release was guilty of not supporting this properly, hence here comes Weld API 5.0.CR2 and Weld Core 5.0.0.CR2.
-
-
-
Weld now automatically fires these events and the JIRA issue for this can be seen here (WELD-2709).
- However, integrators can choose to override this behavior and fire both events themselves in case there is more bootstrapping logic that needs to come together before the container is deemed ready.
- The API interface org.jboss.weld.bootstrap.api.Environment allows implementors to override a specific method which will then prevent Weld from handling these events.
-
-
-
-
-
diff --git a/news/page/4.html b/news/page/4.html
index 24933264..5317505d 100644
--- a/news/page/4.html
+++ b/news/page/4.html
@@ -141,6 +141,42 @@
+
+
+
+ 2022-3-23
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Final ballot of CDI 4 has uncovered untested and unimplemented area in the newly added Startup and Shutdown events.
+
+
+
Our previous release was guilty of not supporting this properly, hence here comes Weld API 5.0.CR2 and Weld Core 5.0.0.CR2.
+
+
+
Weld now automatically fires these events and the JIRA issue for this can be seen here (WELD-2709).
+ However, integrators can choose to override this behavior and fire both events themselves in case there is more bootstrapping logic that needs to come together before the container is deemed ready.
+ The API interface org.jboss.weld.bootstrap.api.Environment allows implementors to override a specific method which will then prevent Weld from handling these events.
+
+
+
+
+
-
-
-
- 2021-4-14
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Thanks to your reports, several flaws were discovered in the new class defining for JDK 11+.
- We have addressed those issues and because we reckon they are potentially blocking, we have released Weld 3.1.7.SP1 and 4.0.1.SP1.
-
-
-
Two main issues were:
-
-
-
- -
-
Producers returning an interface type could sometimes try to define a proxy class with invalid name (WELD-2662)
-
-
- -
-
Proxy class names for hierarchical type structures of interfaces could lead to a jumbled combination of package and name (WELD-2666)
-
-
-
-
-
-
-
-
-
diff --git a/news/page/5.html b/news/page/5.html
index 506bf697..13094668 100644
--- a/news/page/5.html
+++ b/news/page/5.html
@@ -141,6 +141,67 @@
+
+
+
+ 2021-4-14
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Thanks to your reports, several flaws were discovered in the new class defining for JDK 11+.
+ We have addressed those issues and because we reckon they are potentially blocking, we have released Weld 3.1.7.SP1 and 4.0.1.SP1.
+
+
+
Two main issues were:
+
+
+
+ -
+
Producers returning an interface type could sometimes try to define a proxy class with invalid name (WELD-2662)
+
+
+ -
+
Proxy class names for hierarchical type structures of interfaces could lead to a jumbled combination of package and name (WELD-2666)
+
+
+
+
+
+
+
+
+
Weld 4.0.1.Final
@@ -538,104 +599,6 @@ WildFly Patch
-
-
-
- 2020-9-18
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
A new Weld 4 release is now available!
- Latest core version is now 4.0.0.Beta1 and Weld API that ships with it is 4.0.Beta1.
-
-
-
I will not be listing links to issues as usual, because I think more important work was done outside of JIRA tracking this time (although you can check the issues here).
- Instead, let me sum it up in a short list of noticeable changes:
-
-
-
- -
-
All Weld bits are now present in Maven Central
-
-
- -
-
We are able to execute CDI TCKs in EE 9 environment once again and it’s all passing
-
- -
-
We are now able to test servlets with Tomcats and Undertow
-
-
- -
-
Reworked documentation generation tooling
-
-
- -
-
Did some updates on Javadoc generation in API and Core if generated with JDK 11
-
- -
-
Big update pass on tooling and dependencies
-
-
-
-
-
-
On top of that, every bugfix that would go into Weld 3 is of course being added to Weld 4 as well so those aren’t missing either!
-
-
-
WildFly Patch
-
-
-
Sadly we cannot provide a patch for WildFly as there is not yet any official release that would support EE 9.
- As soon as there is one, we will surely follow up with Weld patch!
-
-
-
-
-
-
-
diff --git a/news/page/6.html b/news/page/6.html
index 1162c689..a6e4104b 100644
--- a/news/page/6.html
+++ b/news/page/6.html
@@ -141,6 +141,104 @@
+
+
+
+ 2020-9-18
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
A new Weld 4 release is now available!
+ Latest core version is now 4.0.0.Beta1 and Weld API that ships with it is 4.0.Beta1.
+
+
+
I will not be listing links to issues as usual, because I think more important work was done outside of JIRA tracking this time (although you can check the issues here).
+ Instead, let me sum it up in a short list of noticeable changes:
+
+
+
+ -
+
All Weld bits are now present in Maven Central
+
+
+ -
+
We are able to execute CDI TCKs in EE 9 environment once again and it’s all passing
+
+ -
+
We are now able to test servlets with Tomcats and Undertow
+
+
+ -
+
Reworked documentation generation tooling
+
+
+ -
+
Did some updates on Javadoc generation in API and Core if generated with JDK 11
+
+ -
+
Big update pass on tooling and dependencies
+
+
+
+
+
+
On top of that, every bugfix that would go into Weld 3 is of course being added to Weld 4 as well so those aren’t missing either!
+
+
+
WildFly Patch
+
+
+
Sadly we cannot provide a patch for WildFly as there is not yet any official release that would support EE 9.
+ As soon as there is one, we will surely follow up with Weld patch!
+
+
+
+
+
+
+
Weld 3.1.5.Final
@@ -575,133 +673,6 @@ WildFly Patch
-
-
-
- 2019-8-6
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Weld 3.1.2.Final is coming along with Weld API 3.1.SP1. It is another small release bringing in mainly bugfixes.
- One notable thing is that thanks to guys from Jetty, Weld 3.1.2.Final is ready to operate with lastest Jetty 9 as well as upcoming Jetty 10.
- Other than that we have tried to address some dodgy issues with possible race conditions and leaks - see for yourself!
-
-
-
Fixes and improvements:
-
-
-
- -
-
Weld API/SPI
-
-
- -
-
Weld Core
-
-
- -
-
Fixed a case where some context event notification wouldn’t trigger observers due to race condition (WELD-2557)
-
- -
-
Fixed rare IllegalAccessError problem during interception when methods had (package) private parameters from different methods (WELD-2583)
-
-
- -
-
Attempted to fix a race condition that could happen when trying to concurrently initiate conversation ID generator (WELD-2585)
-
- -
-
Weld now correctly disregards synthetic methods when considering proxyability (WELD-2586)
-
- -
-
Correction to beans.xml parses when using Weld namespace (WELD-2591)
-
-
-
- -
-
Weld SE
-
-
- -
-
Improved classpath scanning to account for manifest file entries (WELD-2589)
-
- -
-
javax.enterprise.inject.scan.implicit=true and org.jboss.weld.se.archive.isolation=false now work together correctly (WELD-2590)
-
-
-
- -
-
Weld Servlet
-
-
-
-
-
-
WildFly Patch
-
-
-
-
If you’re not familiar with patching WildFly, check the FAQ.
-
-
-
-
-
-
-
diff --git a/news/page/7.html b/news/page/7.html
index f482cb16..cf8b5c91 100644
--- a/news/page/7.html
+++ b/news/page/7.html
@@ -141,6 +141,133 @@
+
+
+
+ 2019-8-6
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Weld 3.1.2.Final is coming along with Weld API 3.1.SP1. It is another small release bringing in mainly bugfixes.
+ One notable thing is that thanks to guys from Jetty, Weld 3.1.2.Final is ready to operate with lastest Jetty 9 as well as upcoming Jetty 10.
+ Other than that we have tried to address some dodgy issues with possible race conditions and leaks - see for yourself!
+
+
+
Fixes and improvements:
+
+
+
+ -
+
Weld API/SPI
+
+
+ -
+
Weld Core
+
+
+ -
+
Fixed a case where some context event notification wouldn’t trigger observers due to race condition (WELD-2557)
+
+ -
+
Fixed rare IllegalAccessError problem during interception when methods had (package) private parameters from different methods (WELD-2583)
+
+
+ -
+
Attempted to fix a race condition that could happen when trying to concurrently initiate conversation ID generator (WELD-2585)
+
+ -
+
Weld now correctly disregards synthetic methods when considering proxyability (WELD-2586)
+
+ -
+
Correction to beans.xml parses when using Weld namespace (WELD-2591)
+
+
+
+ -
+
Weld SE
+
+
+ -
+
Improved classpath scanning to account for manifest file entries (WELD-2589)
+
+ -
+
javax.enterprise.inject.scan.implicit=true and org.jboss.weld.se.archive.isolation=false now work together correctly (WELD-2590)
+
+
+
+ -
+
Weld Servlet
+
+
+
+
+
+
WildFly Patch
+
+
+
+
If you’re not familiar with patching WildFly, check the FAQ.
+
+
+
+
+
+
+
-
-
-
- 2018-7-10
-
-
-
- team
-
-
-
- Martin Kouba
-
-
-
-
-
I’m pleased to announce a couple of changes coming to the Weld team.
-
-
-
First of all, Matěj Novotný will be taking over the leadership of the project.
- Matěj has proven himself to be an excellent engineer, contributing not only to Weld projects but also to the CDI specification and TCK development.
- I’m really happy that I can hand over the leadership to this guy!
-
-
-
Matěj’s primary task is leading the project towards "Java 11 world" and to meet the other challenges such as reactive programming model enhancements.
-
-
-
Secondly, Nikoleta Žiaková is joining the team as a quality engineer.
- She’s going to work on expanding our testsuites and improving our continuous integration.
-
-
-
Last but not least, I’m not going to leave the project but stay as a contributor focused on related technologies such as WildFly, Thorntail and MicroProfile.
-
-
-
-
-
diff --git a/news/page/8.html b/news/page/8.html
index 272fe217..174fbc39 100644
--- a/news/page/8.html
+++ b/news/page/8.html
@@ -141,6 +141,47 @@
+
+
+
+ 2018-7-10
+
+
+
+ team
+
+
+
+ Martin Kouba
+
+
+
+
+
I’m pleased to announce a couple of changes coming to the Weld team.
+
+
+
First of all, Matěj Novotný will be taking over the leadership of the project.
+ Matěj has proven himself to be an excellent engineer, contributing not only to Weld projects but also to the CDI specification and TCK development.
+ I’m really happy that I can hand over the leadership to this guy!
+
+
+
Matěj’s primary task is leading the project towards "Java 11 world" and to meet the other challenges such as reactive programming model enhancements.
+
+
+
Secondly, Nikoleta Žiaková is joining the team as a quality engineer.
+ She’s going to work on expanding our testsuites and improving our continuous integration.
+
+
+
Last but not least, I’m not going to leave the project but stay as a contributor focused on related technologies such as WildFly, Thorntail and MicroProfile.
+
+
+
+
+
Weld 3.0.4.Final
@@ -709,136 +750,6 @@ What If I Would Like To…
-
-
-
- 2017-12-18
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Time has come for another round of Weld 2.4 bugfix release.
- But that’s not all - this time there is also new API to go along with this release - Weld API 2.4.SP2.
-
-
-
Among other things you can now obtain interceptor binding from javax.interceptor.InvocationContext, use enriched version of javax.enterprise.event.Event or select javax.enterprise.inject.Instance based on java.lang.reflect.Type.
-
-
-
Notable fixes and improvements:
-
-
-
- -
-
Weld Core:
-
-
- -
-
Improved subclass generation mechanism for generic interceptors (WELD-2414)
-
- -
-
Corrected proxy creation for signed classes (WELD-2425)
-
- -
-
Correct InjectionPoint bean behaviour when used within AfterBeanDiscovery observer (WELD-2429)
-
-
-
- -
-
Weld SE
-
-
- -
-
Weld API/SPI
-
-
- -
-
WeldInstance has several improvements
-
-
- -
-
It now allows you to select() beans based on java.lang.reflect.Type (WELD-2427)
-
- -
-
WeldInstance.Handler had become lazy which means you can now iterate/filter/sort WeldInstance without actually instantiating beans (WELD-2258)
-
-
-
- -
-
There is new interface in the API - WeldEvent - which can be used in place of well known Event but allows you narrow down event type by using select() with java.lang.reflect.Type (WELD-2427)
-
- -
-
API now contains WeldInvocationContext, an enriched version of javax.interceptor.InvocationContext which allows to obtain interceptor binding (WELD-2433)
-
-
- -
-
There is also a String key used to obtain interceptors binding directly from InvocationContext (WELD-2436)
-
- -
-
In order to learn more, please refer to (our documentation)
-
-
-
-
-
- -
-
Other
-
-
-
-
-
-
-
-
diff --git a/news/page/9.html b/news/page/9.html
index 56eddcea..4860d252 100644
--- a/news/page/9.html
+++ b/news/page/9.html
@@ -141,6 +141,136 @@
+
+
+
+ 2017-12-18
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Time has come for another round of Weld 2.4 bugfix release.
+ But that’s not all - this time there is also new API to go along with this release - Weld API 2.4.SP2.
+
+
+
Among other things you can now obtain interceptor binding from javax.interceptor.InvocationContext, use enriched version of javax.enterprise.event.Event or select javax.enterprise.inject.Instance based on java.lang.reflect.Type.
+
+
+
Notable fixes and improvements:
+
+
+
+ -
+
Weld Core:
+
+
+ -
+
Improved subclass generation mechanism for generic interceptors (WELD-2414)
+
+ -
+
Corrected proxy creation for signed classes (WELD-2425)
+
+ -
+
Correct InjectionPoint bean behaviour when used within AfterBeanDiscovery observer (WELD-2429)
+
+
+
+ -
+
Weld SE
+
+
+ -
+
Weld API/SPI
+
+
+ -
+
WeldInstance has several improvements
+
+
+ -
+
It now allows you to select() beans based on java.lang.reflect.Type (WELD-2427)
+
+ -
+
WeldInstance.Handler had become lazy which means you can now iterate/filter/sort WeldInstance without actually instantiating beans (WELD-2258)
+
+
+
+ -
+
There is new interface in the API - WeldEvent - which can be used in place of well known Event but allows you narrow down event type by using select() with java.lang.reflect.Type (WELD-2427)
+
+ -
+
API now contains WeldInvocationContext, an enriched version of javax.interceptor.InvocationContext which allows to obtain interceptor binding (WELD-2433)
+
+
+ -
+
There is also a String key used to obtain interceptors binding directly from InvocationContext (WELD-2436)
+
+ -
+
In order to learn more, please refer to (our documentation)
+
+
+
+
+
+ -
+
Other
+
+
+
+
+
+
+
+
Weld 3.0.2.Final
@@ -694,124 +824,6 @@ Future and Plans
-
-
-
- 2017-6-14
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
We have been busy chasing down some annoying little bugs and it’s high time you got the fruits of those efforts into your hands.
- Say hello to Weld 2.4.4.Final.
-
-
-
Notable fixes and improvements:
-
-
-
- -
-
Weld Core
-
-
- -
-
Fixed bean discovery event ordering when processing producers (WELD-2393)
-
- -
-
Eliminated an NPE for a corner case with abstract decorator (WELD-2273)
-
- -
-
Corrected @Initialized(RequestScoped.class) event firing in @PostConstruct callbacks (WELD-2372)
-
- -
-
Fixed BeanManager.isStereotype() behavior when checking a qualifier annotated with yet another qualifier (WELD-2390)
-
-
-
- -
-
Weld SE
-
-
- -
-
Added a convenience static method WeldContainer.current(), a shortcut for CDI.current() with no need to cast the result (WELD-2399)
-
- -
-
Allowed to specify bean discovery mode for synthetic archives (WELD-2386)
-
- -
-
Fixed bean class discovery problem when adding whole packages (WELD-2395)
-
-
-
- -
-
Weld Servlet
-
-
- -
-
Configuration options
-
-
- -
-
Development tools
-
-
-
-
-
-
WildFly Patch
-
-
-
As usual, a patch for WildFly is available.
- Target platform is WildFly 10.1.0.Final.
- If you’re not familiar with patching WildFly, check the FAQ.
-
-
-
-
-
-
-
diff --git a/news/tags/release/index.html b/news/tags/release/index.html
index c3b8c268..b7ccdbf9 100644
--- a/news/tags/release/index.html
+++ b/news/tags/release/index.html
@@ -141,6 +141,51 @@
+
+
+
+ 2024-11-28
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Turns out we forgot to perform some code cleanup in the CR1 - so here goes 6.0.0.CR2 which removes deprecated code pieces.
+ Note that Weld API is unchanged; the only deprecations there are changes coming in recent CDI versions so we’ve kept that code around for now.
+
+
+
Resolved issues in this version:
+
+
+
+
As per usual, please report any issues you discover with this release so that we can squash those bugs.
+
+
+
+
+
-
-
-
- 2022-10-3
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Weld Core 5.1.0.Final and Weld API 5.0.SP3 are now availabe in Maven Central.
-
-
-
Most notable change, which is also the cause of a minor version bump, is the removal of Weld Probe from our codebase.
- Details are in this JIRA issue and were also communicated via weld-dev email.
-
-
-
In short, Probe hasn’t been maintained for a long time and its UI part is using outdated libraries and would need to be completely re-written which is something that we opted not to do at the moment.
- The JIRA issue has more information as to how we could re-integrate it in the future if there is interest from the community.
-
-
-
-
- |
- Warning
- |
-
- Probe removal affects any integrators that were using Probe up until now! This typically concerns EE integrators such as WildFly or Liberty.
- |
-
-
-
-
-
As usual, here is a list of notable bugfixes in this version:
-
-
-
- -
-
Made decorators more Groovy friendly (WELD-2713)
-
- -
-
Updated Jandex and remove deprecated usages (WELD-2724)
-
- -
-
Added tools to execute TCK lang model in EE container (using WildFly) (WELD-2725)
-
- -
-
Introduced method to WeldManager which allows to obtain instances of all registered contexts regardless of whether they are active (WELD-2726)
-
- -
-
Brought WildFly Arquillian dependency setup up to date and fix affected examples (WELD-2727)
-
- -
-
AbstractResourceServices in Weld API now correctly take into consideration lookup value of @Resource (WELD-2728)
-
- -
-
AbstractResourceServices now supports setter methods for @Resource where the name is defaulted (WELD-2732)
-
- -
-
Corrected the implementation of WeldExpressionFactory#equals (WELD-2729)
-
- -
-
Fixed BeanManager bean types to also include BeanContainer (WELD-2731)
-
- -
-
Avoid logging information about non-bindings member when using BeanManager#isQualifier for annotations that aren’t qualifiers (WELD-2643)
-
- -
-
Removal of Weld Probe (WELD-2733)
-
-
-
-
-
-
-
diff --git a/news/tags/release/page/2.html b/news/tags/release/page/2.html
index 5a5b64ca..8d9201ba 100644
--- a/news/tags/release/page/2.html
+++ b/news/tags/release/page/2.html
@@ -141,6 +141,94 @@
+
+
+
+ 2022-10-3
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Weld Core 5.1.0.Final and Weld API 5.0.SP3 are now availabe in Maven Central.
+
+
+
Most notable change, which is also the cause of a minor version bump, is the removal of Weld Probe from our codebase.
+ Details are in this JIRA issue and were also communicated via weld-dev email.
+
+
+
In short, Probe hasn’t been maintained for a long time and its UI part is using outdated libraries and would need to be completely re-written which is something that we opted not to do at the moment.
+ The JIRA issue has more information as to how we could re-integrate it in the future if there is interest from the community.
+
+
+
+
+ |
+ Warning
+ |
+
+ Probe removal affects any integrators that were using Probe up until now! This typically concerns EE integrators such as WildFly or Liberty.
+ |
+
+
+
+
+
As usual, here is a list of notable bugfixes in this version:
+
+
+
+ -
+
Made decorators more Groovy friendly (WELD-2713)
+
+ -
+
Updated Jandex and remove deprecated usages (WELD-2724)
+
+ -
+
Added tools to execute TCK lang model in EE container (using WildFly) (WELD-2725)
+
+ -
+
Introduced method to WeldManager which allows to obtain instances of all registered contexts regardless of whether they are active (WELD-2726)
+
+ -
+
Brought WildFly Arquillian dependency setup up to date and fix affected examples (WELD-2727)
+
+ -
+
AbstractResourceServices in Weld API now correctly take into consideration lookup value of @Resource (WELD-2728)
+
+ -
+
AbstractResourceServices now supports setter methods for @Resource where the name is defaulted (WELD-2732)
+
+ -
+
Corrected the implementation of WeldExpressionFactory#equals (WELD-2729)
+
+ -
+
Fixed BeanManager bean types to also include BeanContainer (WELD-2731)
+
+ -
+
Avoid logging information about non-bindings member when using BeanManager#isQualifier for annotations that aren’t qualifiers (WELD-2643)
+
+ -
+
Removal of Weld Probe (WELD-2733)
+
+
+
+
+
+
+
-
-
-
- 2021-4-14
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Thanks to your reports, several flaws were discovered in the new class defining for JDK 11+.
- We have addressed those issues and because we reckon they are potentially blocking, we have released Weld 3.1.7.SP1 and 4.0.1.SP1.
-
-
-
Two main issues were:
-
-
-
- -
-
Producers returning an interface type could sometimes try to define a proxy class with invalid name (WELD-2662)
-
-
- -
-
Proxy class names for hierarchical type structures of interfaces could lead to a jumbled combination of package and name (WELD-2666)
-
-
-
-
-
-
-
-
-
diff --git a/news/tags/release/page/3.html b/news/tags/release/page/3.html
index 3addd26b..ad7fdad3 100644
--- a/news/tags/release/page/3.html
+++ b/news/tags/release/page/3.html
@@ -141,6 +141,67 @@
+
+
+
+ 2021-4-14
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Thanks to your reports, several flaws were discovered in the new class defining for JDK 11+.
+ We have addressed those issues and because we reckon they are potentially blocking, we have released Weld 3.1.7.SP1 and 4.0.1.SP1.
+
+
+
Two main issues were:
+
+
+
+ -
+
Producers returning an interface type could sometimes try to define a proxy class with invalid name (WELD-2662)
+
+
+ -
+
Proxy class names for hierarchical type structures of interfaces could lead to a jumbled combination of package and name (WELD-2666)
+
+
+
+
+
+
+
+
+
Weld 4.0.1.Final
@@ -1070,133 +1131,6 @@ WildFly Patch
-
-
-
- 2019-8-6
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
Weld 3.1.2.Final is coming along with Weld API 3.1.SP1. It is another small release bringing in mainly bugfixes.
- One notable thing is that thanks to guys from Jetty, Weld 3.1.2.Final is ready to operate with lastest Jetty 9 as well as upcoming Jetty 10.
- Other than that we have tried to address some dodgy issues with possible race conditions and leaks - see for yourself!
-
-
-
Fixes and improvements:
-
-
-
- -
-
Weld API/SPI
-
-
- -
-
Weld Core
-
-
- -
-
Fixed a case where some context event notification wouldn’t trigger observers due to race condition (WELD-2557)
-
- -
-
Fixed rare IllegalAccessError problem during interception when methods had (package) private parameters from different methods (WELD-2583)
-
-
- -
-
Attempted to fix a race condition that could happen when trying to concurrently initiate conversation ID generator (WELD-2585)
-
- -
-
Weld now correctly disregards synthetic methods when considering proxyability (WELD-2586)
-
- -
-
Correction to beans.xml parses when using Weld namespace (WELD-2591)
-
-
-
- -
-
Weld SE
-
-
- -
-
Improved classpath scanning to account for manifest file entries (WELD-2589)
-
- -
-
javax.enterprise.inject.scan.implicit=true and org.jboss.weld.se.archive.isolation=false now work together correctly (WELD-2590)
-
-
-
- -
-
Weld Servlet
-
-
-
-
-
-
WildFly Patch
-
-
-
-
If you’re not familiar with patching WildFly, check the FAQ.
-
-
-
-
-
-
-
diff --git a/news/tags/release/page/4.html b/news/tags/release/page/4.html
index df3f14d3..2e58a9b8 100644
--- a/news/tags/release/page/4.html
+++ b/news/tags/release/page/4.html
@@ -141,6 +141,133 @@
+
+
+
+ 2019-8-6
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
Weld 3.1.2.Final is coming along with Weld API 3.1.SP1. It is another small release bringing in mainly bugfixes.
+ One notable thing is that thanks to guys from Jetty, Weld 3.1.2.Final is ready to operate with lastest Jetty 9 as well as upcoming Jetty 10.
+ Other than that we have tried to address some dodgy issues with possible race conditions and leaks - see for yourself!
+
+
+
Fixes and improvements:
+
+
+
+ -
+
Weld API/SPI
+
+
+ -
+
Weld Core
+
+
+ -
+
Fixed a case where some context event notification wouldn’t trigger observers due to race condition (WELD-2557)
+
+ -
+
Fixed rare IllegalAccessError problem during interception when methods had (package) private parameters from different methods (WELD-2583)
+
+
+ -
+
Attempted to fix a race condition that could happen when trying to concurrently initiate conversation ID generator (WELD-2585)
+
+ -
+
Weld now correctly disregards synthetic methods when considering proxyability (WELD-2586)
+
+ -
+
Correction to beans.xml parses when using Weld namespace (WELD-2591)
+
+
+
+ -
+
Weld SE
+
+
+ -
+
Improved classpath scanning to account for manifest file entries (WELD-2589)
+
+ -
+
javax.enterprise.inject.scan.implicit=true and org.jboss.weld.se.archive.isolation=false now work together correctly (WELD-2590)
+
+
+
+ -
+
Weld Servlet
+
+
+
+
+
+
WildFly Patch
+
+
+
+
If you’re not familiar with patching WildFly, check the FAQ.
+
+
+
+
+
+
+
Weld 3.1.1.Final
@@ -1439,101 +1566,6 @@ WildFly Patch
-
-
-
- 2017-9-11
-
-
-
- release
-
-
-
- Matej Novotny
-
-
-
-
-
It’s about time we delivered another regular bugfix release for Weld 2.
- And while the list of fixes isn’t exhausting, some of them are quite crucial.
-
-
-
Notable fixes and improvements:
-
-
-
- -
-
Weld Core:
-
-
- -
-
Revise Java 8 default methods plus proxies/sublasing behaviour (WELD-2407 and WELD-2405)
-
- -
-
All POMs in Weld core project should now have correct MIME types; this corrects issues with Nexus 3 (WELD-2417)
-
- -
-
Proxies for signed packages should now be generated in custom packages (WELD-2402)
-
- -
-
The behaviour of Weld Core and integrator provided implementation of org.jboss.weld.bootstrap.api.Environment is back to what it was in Weld 2.4.3.Final (WELD-2401)
-
-
- -
-
We found out this change could cause serious headaches to integrators so we will leave it as it is - sorry for the mess
-
- -
-
For Weld 3, we already have a better solution in place
-
-
-
-
-
- -
-
Weld SE and Servlet
-
-
- -
-
Other
-
-
-
-
-
-
-
-
diff --git a/news/tags/release/page/5.html b/news/tags/release/page/5.html
index 9cec49f3..add456ab 100644
--- a/news/tags/release/page/5.html
+++ b/news/tags/release/page/5.html
@@ -141,6 +141,101 @@
+
+
+
+ 2017-9-11
+
+
+
+ release
+
+
+
+ Matej Novotny
+
+
+
+
+
It’s about time we delivered another regular bugfix release for Weld 2.
+ And while the list of fixes isn’t exhausting, some of them are quite crucial.
+
+
+
Notable fixes and improvements:
+
+
+
+ -
+
Weld Core:
+
+
+ -
+
Revise Java 8 default methods plus proxies/sublasing behaviour (WELD-2407 and WELD-2405)
+
+ -
+
All POMs in Weld core project should now have correct MIME types; this corrects issues with Nexus 3 (WELD-2417)
+
+ -
+
Proxies for signed packages should now be generated in custom packages (WELD-2402)
+
+ -
+
The behaviour of Weld Core and integrator provided implementation of org.jboss.weld.bootstrap.api.Environment is back to what it was in Weld 2.4.3.Final (WELD-2401)
+
+
+ -
+
We found out this change could cause serious headaches to integrators so we will leave it as it is - sorry for the mess
+
+ -
+
For Weld 3, we already have a better solution in place
+
+
+
+
+
+ -
+
Weld SE and Servlet
+
+
+ -
+
Other
+
+
+
+
+
+
+
+
Weld 3.0.1.Final
@@ -1059,89 +1154,6 @@ WildFly Patch
-
-
-
- 2016-9-13
-
-
-
- release
-
-
-
- Martin Kouba
-
-
-
-
-
I am very pleased to announce the first stable version of Weld 2.4 (CDI 1.2).
- See also the release details.
- From now on, 2.4 is the current stable version of Weld and 2.3 is not actively developed anymore.
- Thanks to everyone involved in this release!
-
-
-
-
- -
-
Removed dependency on com.google.guava:guava
-
- -
-
Enhanced version of javax.enterprise.inject.Instance
-
- -
-
Veto AnnotatedType not annotated with a bean defining annotation
-
- -
-
@ActivateRequestScope interceptor binding moved to Weld API and renamed to @ActivateRequestContext
-
- -
-
Improved rolling upgrades support
-
- -
-
Events - reflect the output of CDI-494
-
- -
-
Probe - allow to filter unused beans
-
- -
-
Cleanup, cleanup, cleanup…
-
- -
-
Initial Java 9 support
-
-
-
-
-
Moreover, 2.4.0.Final allows to export the Probe development tool data (to be discussed in one of the following blog posts) and fixes a minor problem in non-EE environments (see also WELD-2227).
-
-
-
In the coming weeks, the Weld team is also going to publish "Weld tips" - a series of concise articles.
- The intention is to familiarize developers with less known Weld features.
- There will be no hot news, just useful existing features (repetition is the mother of wisdom ;-).
-
-
-
WildFly Patch
-
-
-
As usual, a patch for WildFly is available. This time the target platform is WildFly 10.1.0.Final. If you’re not familiar with patching WildFly, check Markus’s tutorial.
-
-
-
-
-
-
-
diff --git a/news/tags/release/page/6.html b/news/tags/release/page/6.html
index 4df51e01..dd80b5ac 100644
--- a/news/tags/release/page/6.html
+++ b/news/tags/release/page/6.html
@@ -141,6 +141,89 @@
+
+
+
+ 2016-9-13
+
+
+
+ release
+
+
+
+ Martin Kouba
+
+
+
+
+
I am very pleased to announce the first stable version of Weld 2.4 (CDI 1.2).
+ See also the release details.
+ From now on, 2.4 is the current stable version of Weld and 2.3 is not actively developed anymore.
+ Thanks to everyone involved in this release!
+
+
+
+
+ -
+
Removed dependency on com.google.guava:guava
+
+ -
+
Enhanced version of javax.enterprise.inject.Instance
+
+ -
+
Veto AnnotatedType not annotated with a bean defining annotation
+
+ -
+
@ActivateRequestScope interceptor binding moved to Weld API and renamed to @ActivateRequestContext
+
+ -
+
Improved rolling upgrades support
+
+ -
+
Events - reflect the output of CDI-494
+
+ -
+
Probe - allow to filter unused beans
+
+ -
+
Cleanup, cleanup, cleanup…
+
+ -
+
Initial Java 9 support
+
+
+
+
+
Moreover, 2.4.0.Final allows to export the Probe development tool data (to be discussed in one of the following blog posts) and fixes a minor problem in non-EE environments (see also WELD-2227).
+
+
+
In the coming weeks, the Weld team is also going to publish "Weld tips" - a series of concise articles.
+ The intention is to familiarize developers with less known Weld features.
+ There will be no hot news, just useful existing features (repetition is the mother of wisdom ;-).
+
+
+
WildFly Patch
+
+
+
As usual, a patch for WildFly is available. This time the target platform is WildFly 10.1.0.Final. If you’re not familiar with patching WildFly, check Markus’s tutorial.
+
+
+
+
+
+
+
-
-
-
- 2015-9-18
-
-
-
- release
-
-
-
- Martin Kouba
-
-
-
-
-
Weld 2.3.0.Final has been just released! From now on, 2.3 is the current stable version of Weld and 2.2 is not actively developed anymore - i.e. no new features are added, only bugs will be fixed. Weld 2.3 will remain a CDI 1.2 implementation. We are incrementing the minor version due to several new features added. Weld 2.3 is also included in WildFly 10 application server.
-
-
-
Notable features and changes:
-
-
-
- -
-
Java 6 support was dropped - Java 7 is the minimal requirement for building and running Weld 2.3
-
- -
-
Weld 2.3 comes with a special mode for application development, the Probe development tool allows to inspect application CDI components at runtime
-
- -
-
Weld SE Bootstrap API was enhanced in many ways - new features are mostly backported from Weld 3 development branch
-
- -
-
Weld Servlet now supports Undertow web server
-
- -
-
Revised delivery of @Initialized/@Destroyed events for @ApplicationScoped in an EAR (see also WELD-1821)
-
-
-
-
-
-
Weld 2.2.16.SP1
-
-
-
In addition, Weld 2.2.16.SP1 has been also released. It’s a bugfix release for 2.2 branch.
-
-
-
-
-
-
-
diff --git a/news/tags/release/page/7.html b/news/tags/release/page/7.html
index f6013968..cef02cc8 100644
--- a/news/tags/release/page/7.html
+++ b/news/tags/release/page/7.html
@@ -141,6 +141,69 @@
+
+
+
+ 2015-9-18
+
+
+
+ release
+
+
+
+ Martin Kouba
+
+
+
+
+
Weld 2.3.0.Final has been just released! From now on, 2.3 is the current stable version of Weld and 2.2 is not actively developed anymore - i.e. no new features are added, only bugs will be fixed. Weld 2.3 will remain a CDI 1.2 implementation. We are incrementing the minor version due to several new features added. Weld 2.3 is also included in WildFly 10 application server.
+
+
+
Notable features and changes:
+
+
+
+ -
+
Java 6 support was dropped - Java 7 is the minimal requirement for building and running Weld 2.3
+
+ -
+
Weld 2.3 comes with a special mode for application development, the Probe development tool allows to inspect application CDI components at runtime
+
+ -
+
Weld SE Bootstrap API was enhanced in many ways - new features are mostly backported from Weld 3 development branch
+
+ -
+
Weld Servlet now supports Undertow web server
+
+ -
+
Revised delivery of @Initialized/@Destroyed events for @ApplicationScoped in an EAR (see also WELD-1821)
+
+
+
+
+
+
Weld 2.2.16.SP1
+
+
+
In addition, Weld 2.2.16.SP1 has been also released. It’s a bugfix release for 2.2 branch.
+
+
+
+
+
+
+
Weld 3.0.0.Alpha12 - CDI 2.0 EDR1 Reference Implementation!
diff --git a/sitemap.xml b/sitemap.xml
index 47e5809c..9706360a 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,37 +2,37 @@
https://weld.cdi-spec.org/bug/
- 2024-11-13
+ 2024-11-28
0.5
weekly
https://weld.cdi-spec.org/community/
- 2024-11-13
+ 2024-11-28
0.5
weekly
https://weld.cdi-spec.org/dist/
- 2024-11-13
+ 2024-11-28
1
daily
https://weld.cdi-spec.org/documentation/
- 2024-11-13
+ 2024-11-28
0.5
weekly
https://weld.cdi-spec.org/download/
- 2024-11-13
+ 2024-11-28
0.5
weekly
https://weld.cdi-spec.org/
- 2024-11-13
+ 2024-11-28
0.5
weekly
@@ -594,9 +594,15 @@
1
weekly
+
+ https://weld.cdi-spec.org/news/2024/11/28/weld-600CR2/
+ 2024-11-28
+ 1
+ weekly
+
https://weld.cdi-spec.org/news/
- 2024-11-13
+ 2024-11-28
1
daily
+ 
+ 
+ 
-