Weld seample in WebSphere 7 possible

[titou09]

Q:

- in theory, is it possible to run the Weld samples in WebSphere v (JEE5 compliant)

I tried to compile the jsf example and have a problem with the javax.inject.* classes used by the examples.. Those are coming from the JSR-330 specs

Is there a JSR-330 RI somewhere I could include in my ear file?

I've seen those classes in the weld-servlet.jar file with other 3rd-party classes (javassist etc). Is this jar supposed to be a jar to include as dependency even if in the JSF example,  classes are held in an ejb module?

We have many seam 2 application in production on clustered WebSphere v7 and I'm starting to look a tthe migration to weld/seam 3...

[nickarls]

A: No

It is not a simple matter of getting the stuff to compile, CDI has heavy container integration which means that it's the server that has to bootstrap the CDI application with a SPI, providing services to it. This is done with a deployer, a component that sits between the AS and the application. I'm not aware that there is such a component for WebSphere. There will be one (per definition) if they make a Java EE 6 server.

[titou09]

Thanks for your answer.

This is a very bad news for us non glassfish v3 users (and in the future non JBoss v6 users when it will become GA..).

This means that we will have to wait months (a few years ?) before being able to use seam 3 in production.

I hope the development of seam 2.x will continue to support users like us that based our dev on seam 2.x as we will be stuck with it a long time.

Fortunately we are very happy with the current version of seam 2.x but I wanted to move our stack to JSF 2.0 and JPA 2.0 as we startt a new big project. I don't know if seam 2.x is compatible JPA 2.0. I'll make some tests and if minors changes are needed in seam I could commit some code in seam for this.

I'll post a question on the dev mailing list about the plan to maintain seam 2 (and finally at some point take a decision on seam 2.0.3...) and the compatibility of seam 2.2 and JPA 2.0.

[genman]

Given that Weld works on Java SE, I can imagine it might just work on Websphere in some way.

It seems easy to bootstrap Weld using a Servlet listener, use interceptors for injecting into EJB, and generally hook into the container at least as well as Seam does.

[gavin.king]

in theory, is it possible to run the Weld samples in WebSphere v (JEE5 compliant)

Well, in theory you can run Weld in any SE 5 JVM, but you will miss out on the container integration, most importantly the ability to use EJBs as CDI beans (I'm also not sure how well the classpath scanning will work).

Is there a JSR-330 RI somewhere I could include in my ear file?

The jar containing the 330 annotations is available here.

This means that we will have to wait months (a few years ?) before being able to use seam 3 in production.

I don't expect you to have to wait years! Remember that we will be able to release bits of seam 3 incrementally. It doesn't need to be a monolithic release.

[asookazian]

Gavin King wrote on Dec 27, 2009 05:41:


I don't expect you to have to wait years! Remember that we will be able to release bits of seam 3 incrementally. It doesn't need to be a monolithic release.

I'm assuming Seam 3 will adopt the milestone strategy in terms of releases, similar to JBoss AS 6.

What exactly the phased release plan is for Seam 3, I'm not sure but would like to know...

[gavin.king]

Arbi Sookazian wrote on Dec 27, 2009 18:37:

Gavin King wrote on Dec 27, 2009 05:41:


I don't expect you to have to wait years! Remember that we will be able to release bits of seam 3 incrementally. It doesn't need to be a monolithic release.

I'm assuming Seam 3 will adopt the milestone strategy in terms of releases, similar to JBoss AS 6.

What exactly the phased release plan is for Seam 3, I'm not sure but would like to know...

Not exactly. Seam is a set of independent portable extensions, which can be released independently.