WELD-000119: Not generating any bean definitions from because of underlying class loading error

Question

I'm new in using MyEclipse and Java EE

I'm trying to deploy my web application on wildfly 8.0.0. in MyEclipse.

Unfortunately, I'm getting this error after I took some code changes from SVN (I'm not sure this is the reason), before that it was working fine:

[org.jboss.weld.Bootstrap] (weld-worker-2) WELD-000119: Not generating any bean definitions from (.....) because of underlying class loading error: Type WebArchive from [Module "deployment.Test.war:main" from Service Module Loader] not found.  If this is unexpected, enable DEBUG logging to see the full error.

When I (Run) the server, the deployment succeeded although the console produces some lines of the same error, but when i (Debug) the server, it keeps generating the same error.

Can someone help me please

Thanks.

score 2 · Answer 1 · edited Jun 26 '16 at 18:43

It may be that the class loader can't find "WebArchive" because it needs to be added as a module to the WildFly configuration. You do that like this:

module add --name=org.apache.commons.lang3.commons-lang3 --resources=C:\Users\b\.m2\repository\org\apache\commons\commons-lang3\3.4\commons-lang3-3.4.jar

In addition, you'll probably need to add WebArchive as a dependency in the <build> section of your pom.xml.

Here's the relevant section of my pom.xml:

  <build>
    <!-- Maven will append the version to the finalName (which is the name
        given to the generated WAR, and hence the context root) -->
    <plugins>
        <plugin>
            <artifactId>maven-war-plugin</artifactId>
            <version>${version.war.plugin}</version>
            <configuration>
            <!-- Java EE doesn't require web.xml, Maven needs to catch up! -->
                <failOnMissingWebXml>false</failOnMissingWebXml>
                <archive>
                    <manifestEntries>
                        <Dependencies>com.fasterxml.jackson.datatype.jackson-datatype-jsr310,org.hibernate,org.apache.commons.lang3.commons-lang3</Dependencies>
                    </manifestEntries>
                </archive>
            </configuration>
        </plugin>
        <!-- The WildFly plug-in deploys the WAR to a local WildFly container -->
        <!-- To use, run: mvn package wildfly:deploy -->
        <plugin>
            <groupId>org.wildfly.plugins</groupId>
            <artifactId>wildfly-maven-plugin</artifactId>
            <version>${version.wildfly.maven.plugin}</version>
        </plugin>
    </plugins>
</build>

If you can't figure it out, try posting your pom.xml and jboss-deployment-structure.xml (if you have one).

BTW, I'm doing quite a bit of guessing here. What would help a lot is posting your pom.xml. — rakehell, Jun 25 '16 at 00:18

score 0 · Answer 2 · edited May 23 '17 at 12:02

0

This error message does not hint to start your server in debug mode, but to set the log level of org.jboss.weld.Bootstrap or the root logger to debug. See WildFly 8 Logging Levels for how to do that

edited May 23 '17 at 12:02

Community

1
1

answered Mar 29 '16 at 18:22

user140547

7,750
3
28
80

Do you have any "underlying class loading error" log messages listed in that log output? BTW, I don't think turning on additional logging is going to help. – rakehell Jun 24 '16 at 22:52

score 0 · Accepted Answer · answered Nov 14 '16 at 10:11

0

The problem was because I'm starting my server in debug mode and the breakpoints were activated

answered Nov 14 '16 at 10:11

Maha

519
2
11
23

WELD-000119: Not generating any bean definitions from because of underlying class loading error

3 Answers3