[seam-dev] weld 2.0 / soldr 3.x not compatible

[John D. Ament]

I'm pretty sure CDI 1.1 will break a lot of current CDI extensions due to
the behavioral changes.  Do you need exception handling?  Did you try
turning off the exception handling extension?


On Thu, Jun 6, 2013 at 3:41 AM, Korbinian Bachl
<korbinian.bachl at gmail.com>wrote:

> 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.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=364696#action_364696) 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
>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20130606/cc2c0f2e/attachment.html