weld 2.0 / soldr 3.x not compatible
by Korbinian Bachl
Hello,
during our test for Glassfish 4.0 we found out that seam-soldr/ now
jboss-soldr isn't compatbile with weld. We loggedn ans issue at glassfish (
https://java.net/jira/browse/GLASSFISH-20577?page=com.atlassian.jira.plug...)
and they pointed me to this list.
Problem is that soldr calls getBeans() during init and WELD 2 now throws an
exception for this:
org.jboss.weld.exceptions.IllegalStateException: WELD-001332 BeanManager
method getBeans() is not available during application initialization
Sadly the weld 2 people didn't think about backwards compatibility in that
position (why not just throw a big warning?);
Is there any way soldr3.x can get a last compatibilitiy fix?
At least it was previous weld-extensions and therefore seen as the
de-facto standard. I know that the future should be Apache DeltaSpike, but
that wouldnt be a drop in replacement like a new 3.x version of soldr would
be.
Best,
KBachl
11 years, 5 months
Seam 2.3.1.CR1 was tagged and went through release testing
by Marek Novotny
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Seam devs,
I created tag 2.3.1.CR1 (
https://github.com/seam2/jboss-seam/tree/JBoss_Seam_2_3_1_CR1 ) and all
staging/testing with help of Tomas Remes from Seam QE didn't find out
any blocker or major issue for stop the 2.3.1.CR1 release.
I will follow up with final release steps like uploading documentation,
announcement etc..
- --
Marek Novotny
- --
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlGxfwAACgkQU4HO8G8hNxVCEgCgrA2d9yyyGUY+667/2jtGNOU/
t1MAoK0iWk1nksxF8CqFtrpc8TKIjlp+
=6G0p
-----END PGP SIGNATURE-----
11 years, 5 months
