[jboss-jira] [JBoss JIRA] (WFLY-13641) WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
Matěj Novotný (Jira)
issues at jboss.org
Sat Jul 4 15:49:22 EDT 2020
[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198832#comment-14198832 ]
Matěj Novotný commented on WFLY-13641:
--------------------------------------
Hi,
so, you have two deployments, an EAR (with lib) and then a separate WAR. WAR declares a dep on EAR/lib via {{jboss-deployment-structure.xml}}. Do I get that right?
Fairly speaking, I am not familiar with how this should (if it should) work together. An opinion of someone well-versed in this would be nice - e.g. can you even load the jandex index of a completely different deployment?
Looking at {{ExtenalBeanArchiveProcessor}}, [the code|https://github.com/wildfly/wildfly/blob/20.0.0.Final/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/processors/ExternalBeanArchiveProcessor.java#L273-L285] you mention means that we are unable to load the Jandex index, hence we try to create it on the fly and fail there as well.
> 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)
More information about the jboss-jira
mailing list