[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
Jens Viebig (Jira)
issues at jboss.org
Wed Jul 8 05:42:12 EDT 2020
[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205502#comment-14205502 ]
Jens Viebig edited comment on WFLY-13641 at 7/8/20 5:38 AM:
------------------------------------------------------------
Here is some documentation about cross-module CDI and jboss-deployment-structure
[https://docs.wildfly.org/17/Developer_Guide.html#CDI_Reference]
>From my understanding cross-module CDI should only ever be activated if you specify meta-inf="import" on a dependency. But this is not the case for our deployments
was (Author: jviebig):
Here is some documentation about cross-module CDI and jboss-deploymet-structure
[https://docs.wildfly.org/17/Developer_Guide.html#CDI_Reference]
>From my understanding cross-module CDI should only ever be activated if you specify meta-inf="import" on a dependency. But this is not the case for our deployments
> 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