Weld and JBoss 4.2.x

[asookazian]

say we have an existing Seam 2.x, JSF 1.2, JPA 1.0, EJB 3.0, EE 5 app server (JBoss 4.2.x) envmt.

can I deploy Weld apps in this exact envmt so I can run my Weld apps and Seam 2.x apps side-by-side in the same JBoss instance (server/default/deploy)?

or is JBoss 5.x a hard requirement?

I have a feeling no due to the JSF RI differences, etc...

What if I package the JSF 2.0 RI libs into my EAR/WAR and then deploy onto JBoss 4.x?

[nickarls]

The weld deployers aren't written for 4.2.x, it won't boot.

[asookazian]

ok, so what about all the JBoss shops that have 4.x deployed in dev and prod envmts?  So that means if they want to start doing a Weld app with JSF 2.0 and JPA 2.0 then they will need to upgrade their app servers or create new envmts for JBoss 5.x.

this seems like a limiting factor in terms of adoption of CDI/Weld...

[gavin.king]

Correct. Sometimes you have to upgrade software to get new features. That's life.

[nickarls]

Of course, you can port the weld deployers to 4.2 (probably) if you are familiar with the AS bootstrapping. But in the end, upgrade is more simple. OK, many organizations hang fanatically onto some fixed version of an appserver but that usually a limitation of wetware and not hardware.

[pmuir]

Alternatively, you could use the Weld servlet support in JBoss AS 4.2 - no EJB support of course. Give it a whirl, write a tutorial, post it on the site :-)

[fiorenzino]

I tried in jboss 4.2.3 with jsf 2 (in jsf-libs) and with weld-servlet, and the numberguess example works.

But with jsf 1.2 don't works.

My organization will wait jboss 6 (stable release) to upgrade all systems/applications, but i don't want wait 1 year to start use weld in production....

bye