[
https://issues.jboss.org/browse/WELD-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687015#comment-12687015
]
Mark Struberg commented on WELD-1113:
-------------------------------------
will try to reproduce it later today, currently in another project.
> 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
> Assignee: Marko Lukša
>
> 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
_______________________________________________
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
