[
https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi...
]
Matěj Novotný commented on WFLY-13641:
--------------------------------------
I see, good catch! According to that, those beans shouldn't be picked up at all.
Looking at {{ExternalBeanArchiveProcessor}}, there is no processing regarding
jboss-deployment-structure so that has to be done earlier (don't know where yet). This
processor works on the deployment unit and all its subdeployments and dependencies. Maybe
you have some dependency between the two projects that causes the other project to be
scanned for beans as well? The reproducer you mentioned would be neat.
WFLYWELD0055: Could not index class [Someclass] from an external bean
archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
-----------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-13641
URL:
https://issues.redhat.com/browse/WFLY-13641
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 20.0.0.Final
Reporter: Jens Viebig
Assignee: Matěj Novotný
Priority: Major
When referencing a jar with CDI scan mode "annotaded" inside an ear from an
external war via jboss-deployment-structure.xml a warning will be printed for every
class:
WFLYWELD0055: Could not index class [Someclass] from an external bean archive:
vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
Seems VFS cannot get hold of the classes.
The warning is logged in ExternalBeanArchiveProcessor which catches an EOFException from
the inputstream loading the class. (Line 284). Seems the input stream is not able to load
a single byte from the class
--
This message was sent by Atlassian Jira
(v7.13.8#713008)