[weld-issues] [JBoss JIRA] (WELD-1113) Specializing beans in different bean archives is still broken

Sat Apr 21 13:45:17 EDT 2012

Mark Struberg created WELD-1113:
-----------------------------------

             Summary: Specializing beans in different bean archives is still broken
                 Key: WELD-1113
                 URL: https://issues.jboss.org/browse/WELD-1113
             Project: Weld
          Issue Type: Bug
            Reporter: Mark Struberg

This is a follow up on WELD-912.

It appears that this is still broken!

I tried it first on glassfish-3.1.1. with an upgraded weld-osgi-bundle.1.1.7.Final.

I get the following error reported:

remote failure: Error occurred during deployment: Exception while loading the app : WELD-000047 Specializing bean must extend another bean:  Managed Bean [class at.ac.tuwien.tiss.core.fe.codi.TissCodiWindowContextConfig] with qualifiers [@Any @Default]. Please see server.log for more details.

But my class extends the parent class:

public class TissCodiWindowContextConfig extends WindowContextConfig { ..

The TissCodiWindowContextConfig is in my project jar, the parent class in codi-jsf.jar, both in my WEB-INF/lib folders of my webapp.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira