Our CDI integration is currently bound to Weld -- which JBossAS and Glassfish use. I do not believe WebSphere uses Weld to provide its CDI services, so we do not currently have CDI integration support on WebSphere at this time. It is certainly something we can look into supporting if there is enough interest.

Hi Mike,

WebSphere uses a slightly modified version of Apache OpenWebBeans.

To be honest I am a little bit puzzled here, because the Errai-CDI documentation at no point states that there is a dependency to Weld.

The according sections only mention "JSR-299", "CDI Containers" and "Java EE 6 Application Servers", so we were optimistic to get it to work with some effort.

It might be a big help to others to state this "detail" more clearly in the documentation.

Concerning our problem: Do you think it is in any way realistic to have a more general CDI support within this year?
Can you tell us if "pure" Errai will work out of the box within a WebSphere AS or are here other dependencies as well?

Thanks in advance - we already spent quite some effort into our project and do rely on WebSphere as a technical base.

To be honest I am a little bit puzzled here, because the Errai-CDI documentation at no point states that there is a dependency to Weld.

The according sections only mention "JSR-299", "CDI Containers" and "Java EE 6 Application Servers", so we were optimistic to get it to work with some effort.

It might be a big help to others to state this "detail" more clearly in the documentation.

This is fair. We were really talking about the programming model from our perspective with those references. The actual integration module is called "weld-integration" in our project for what it's worth. But yes, there are specific features of Weld which we currently rely upon to make things work as advertised.

Jörn Tysper wrote:

 

Concerning our problem: Do you think it is in any way realistic to have a more general CDI support within this year?

We really cannot make any firm committments in terms of support for additional appservers and timelines therein. However, we would enthusiatically support any contributions to allow our CDI extensions work with non-Weld containers.

But to be clear: this is something we'd really like to support.

Jörn Tysper wrote:

 

Can you tell us if "pure" Errai will work out of the box within a WebSphere AS or are here other dependencies as well?

Errai IOC (the basic dependency injection framework) in the client, as well as the message bus and RPC can certainly work with any appserver. However, that framework uses a thin standalone Guice-based server side framework. Although, you can eschew that and rely purely on the server-side APIs (ie. bus.subcribe()) etc. There are people who do use the server-side components barebones in this manner.

The client-side GWT enhancements we have added (sans CDI eventing) can certainly operate on their own with no server-side integration.

Hi Mike,

to me missing support for Websphere ist surprising too, since in addition to the afore mentioned arguments I relied on a statement of yours promising support of Websphere up from Version 1.1. (http://java.dzone.com/articles/elegant-async-errai).

Checking again today I stumbled upon the following issue https://issues.jboss.org/browse/ERRAI-56

Looking at the activities on that issue I see, that you closed the issue in july 2011 since it outdated.

I would appreciate to see that issue reopened and assigned (ideally solved).

Having Websphere NOT on the list of supported application servers in my opinion serves as a blocker for using Errai for any projects having to be able to run at least potentially on Websphere. In fact it has the smell of proprietary software (which nobody expects here ;-)

Well, I certainly take offense to the the suggestion we're trying to build something proprietary. The article your reference about WebSphere support was back when Errai merely had the bus feature -- and indeed ErraiBus supports WebSphere.

We're talking about the CDI module which came after. In the development of Errai CDI, we ran into certain things that simply were not possible with the CDI 1.0 SPI, which required us to use Weld-specific APIs to achieve the fidelity of integration we were aiming for. Indeed, I have been working with Pete Muir to push for changes to the CDI specification which would close some of these gaps and hopefully remove the neeed to use container-specific integration.

This remains one of our goals -- to make CDI as portable of a specification (both in the SPI side and the user side) as possible.

I repeat my invitation for contributions to help us close the compatibilty gap with WebSphere.

Mike, be assured I have no intent to offend either you or your team.

I have every interest to get this issue addressed, since on our project we have to support websphere and would like to benefit from the advantages Errai offers at the same time.