The Apache OpenWebBeans Team is proud to announce the release of Apache OpenWebBeans-2.0.8.
Apache OpenWebBeans-2.0.x is an Apache License v2 licensed implementation of the JSR-365 CDI-2.0 specification.
OpenWebBeans has a modular structure and provides Dependency Injection scaling from Java SE environments up to Java EE8 server clusters with complicated ClassLoader hierarchies or OSGi environments.
This is a maintenance release targetting the Contexts and Dependency Injection CDI 2.0 specification!
CDI is a JavaEE standard (JSR-365) but fully available under Apache License v2.0.
Apache OpenWebBeans-2.0.8 implements the CDI-2.0 API, and passes the JSR-330 and JSR-365 TCKs.
Apache Meecrowave is a small java enterprise application server framework fully based on Apache Tomcat9 and other JavaEE 8 technologies.
And all that in less than 10MB. That means it is ideally suited for Microservices and standalone applications.
Meecrowave can be either started via a maven plugin (for ease of development), programmatically as embedded server, bundled as application with your business code or as runner to start up portable WAR or JAR applications.
Our main change for this bugfix release is adding preliminary Java11 support.
The Apache OpenWebBeans Team is proud to announce the release of Apache OpenWebBeans-2.0.7.
Apache OpenWebBeans-2.0.7 implements the CDI-2.0 API, and passes the JSR-330 and JSR-365 TCKs.
[OWB-1252] - WebContextsService lazyStartRequestContext fails on first access.
The Apache OpenWebBeans team has been quite busy with big refactorings. Big improvements have been made to the proxying mechanism, the Bean scanning and the AnnotatedType handling. We managed to improve the overall performance again and now deliver almost native Java like performance for our NormalScoping proxies.
Let's take a close look at a few details of the parts we already finished and explain them briefly.
In OpenWebBeans 1.0.x and 1.1.x a single Bean only had one single Proxy handling for all tasks - The NormalScopedBeanInterceptorHandler. This did handle all the stuff like Interceptors, Decorators provide subclassing for abstract Decorators but also did the NormalScope handling.
As result of this unified handling we only stored the native Contextual Instances in the Contexts (Session, Request map, Conversation map, etc). The negative side effect of this approach was that we had to introduce a quite hacky mechanism to regain access to the CreationalContext. Needless to say that this was not only complex but also error prone.
In OpenWebBeans-1.2.0 we now maintain 2 proxies. The first one solely handles NormalScoping, then 2nd one does all the Interceptor and Decorator stuff. The most important change is that we apply the DecoratorProxy directly 1:1 on the Contextual Instance and thus don't need to do any of those weird CreationalContext hacks anymore. Instead the already intercepted/decorated instance gets stored in the Context.
All NormalScope proxies now implement the Interface OwbNormalScopeProxy and have a name *$OwbNormalScopeProxy*.
All Interceptor and/or Decorator proxies implement the Interface OwbInterceptorProxy and have a name *$OwbInterceptProxy*.
Additionally to those 2 proxies we also introduced a new separate proxy kind for creating subclasses for abstract Decorators which now implement the marker interface OwbDecoratorProxy.
There is no bells and whistle and especially no reflection - just pure plain Java bytecode which is blazingly fast!
Btw, we do very similar stuff for non-intercepted methods of intercepted/decorated classes. And we also improved the handling of intercepted methods and are now more than twice as fast as OWB-1.1.7 (which was already very fast).
In the past we had 2 ways to create beans. If an Extension used ProcessAnnotatedType to tweak the AnnotatedType of a class then we built the Bean<T> from the modified AnnotatedType<T>. For cases where the AnnotatedType did not get modified we took a completely different part and created the Bean from the Class reflection information. This part came from a time where there was no AnnotatedType in the spec yet.
In OWB-1.2.0 we now do all the Bean<T> construction based on the AnnotatedType - regardless if it got provided by a CDI-Extension or remained unchanged. This made our codebase much easier to maintain! Arne also did a great job by introducing and cleaning up all the BeanBuilders and making the final Bean<T> immutable.
Create the initial AnnotatedTypes from the information already collected by xbean-finder instead of doing expensive Class reflection.
We initially targeted CDI-1.1 with this release. But during the development we figured that we do not yet need to. All the parts introduced so far are perfectly working with CDI-1.0 as well. Thus it looks like we gonna release OWB-1.2.0 as still being CDI-1.0. But we are well prepared to support the new features of CDI-1.1 very quickly as we already did all the preparations. Sometimes we internally already use CDI-1.1 mechanisms (like the BeanAttributs) and only have to add 'implements RandomCdi11FeatureInterface'. This will likely be shipped as OWB-2.0.0 though when the spec hits an almost final status and the TCK is available.
That's a pretty easy thing. If you have the apache.snapshots maven repo in your build, then you can just reference owb 1.2.0-SNAPSHOT in your build and you're done!
I am pleased to announce the 1.0.0-M2 release of OpenWebBeans. OpenWebBeans will be an ASL-licensed implementation of the Context and Dependency Injection for Java EE Platform Specification which is defined as JSR-299.
This M2 release contains the parts of the specification that enables the developers to start and see more functional aspects of the JSR-299 than M1 release. Please look at the README file to get more about release information.
This release also contains full blown JSF application which is developed by JSF + OWB + JPA.
In addition to the implementation of the specification, the project aims to create a new set of Web Beans exposing functionality of other Apache Foundation projects.
Feel free to ask any questions about the OpenWebBeans and M2-Release via our user forums.