Weld Extensions block use of Seam3

[andrewwheeler]

I can't deploy Seam3 Faces on JBoss6-M5 because it depends on weld extensions which is failing.

Two default beans with the same type and qualifiers: Type: class javax.el.FunctionMapper Qualifiers: [@org.jboss.weld.extensions.el.Mapper()] Beans are Managed Bean [class org.jboss.weld.extensions.el.DummyFunctionMapper] with qualifiers [@Any @Synthetic] and Managed Bean [class org.jboss.weld.extensions.el.DummyFunctionMapper] with qualifiers [@Any @Synthetic]

Looks likes this was reported as JIRA:
https://jira.jboss.org/browse/JBAS-8510. I would have expected this to be fixed in Beta1 as this was released well after this JIRA.

This is a bit of a show stopper for using Seam3. I was really looking forward to using Seam3 features, but I'm stuck. How are other Seam3 users deploying? Does this work on JBoss5 or older versions of JBoss6?

Does anyone has any cute tricks to sort this one?

[shane.bryzak]

I'm guessing that el-api.jar is being included in your application.  If that's the case, just add an exclusion for it in your pom.xml.

[andrewwheeler]

Thanks, but I don't think it is anything to do with the el-api.jar as 1) it is not in my lib dir; and 2) it does not have a beans.xml so it shouldn't be scanned. Anyway I manually excluded the extensions in my WAR beans.xml using:

<weld:scan>
  <!-- This should not be scanned normally as it does not have a beans.xml. Re-check for failure on version update. -->
  <weld:exclude name="org.jboss.weld.extensions.**"/>
</weld:scan>

[oranheim]

Hi Andrew,

Seam 3 and Weld somewhat works as long you use JBoss 6 M4 and Weld Extensions Alpha 2. I'm certain you will not succeed getting Weld Extensions Beta 1 to work with Seam 3 Alpha 3 deployed in JBoss M5.

According to roadmap, JBoss RC1 should have been released Nov 15, so I hope we can expect it anytime soon and getting upgraded modules with proper dependencies.

Cheers,
Ove