[
https://jira.jboss.org/browse/JBAS-8510?page=com.atlassian.jira.plugin.sy...
]
Marius Bogoevici edited comment on JBAS-8510 at 10/14/10 8:39 PM:
------------------------------------------------------------------
OK, I see what you mean. It looks like the process of creating an AnnotatedType from a
class that is not part of a jar with a beans.xml will add the class to the list of classes
returned by BDA.getBeanClasses(), and will instruct Weld to create a Managed Bean for it.
archive.addClass() from loadBeanDeploymentArchive() seems to do this.
Edit: clarity
was (Author: marius.bogoevici):
OK, I see what you mean. It looks like the process of creating an AnnotatedType from a
class that is not part of a jar with a beans.xml will add the class to the list of classes
returned by BDA.getBeanClasses(), and will instruct Weld to create a Managed Bean for it.
Archive being scanned even though no beans.xml is present
---------------------------------------------------------
Key: JBAS-8510
URL:
https://jira.jboss.org/browse/JBAS-8510
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Weld/CDI
Reporter: Stuart Douglas
Assignee: Ales Justin
When using the latest jboss as snapshot from hudson weld-extensions tests fail.
It appears this is because the weld-extensions jar is being scanned and the annotated
types added even though there is no beans.xml in the archive.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira