[
https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi...
]
Matěj Novotný commented on WFLY-13641:
--------------------------------------
[~jviebig] I have sent
https://github.com/wildfly/wildfly/pull/13406 which should fix the
issue you are seeing, although I am not sure it is the best solution.
If you build WFLY from that branch ({{mvn clean install -DskipTests}}) and then try to
deploy to it (whole server is then under
{{wildfly/dist/target/wildfly-21.0.0.Beta1-SNAPSHOT}}), you should see the warning go away
and the beans will not be picked up.
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)