Closed ozzi- closed 4 years ago
Saw in the releases that you mention wildfly16 support, checked with wildfly16, same error
The error:
.....NoClassDefFoundError: Lorg/eclipse/microprofile/config/Config
indicates that the Microprofile v 2.2 is missing.
please make sure you are using:
or
Wildfly 16 is definitely to old. I will fix this in documentation too.
In your installation there should be the following directory:
/wildfly/modules/system/layers/base/org/eclipse/microprofile/config/
This will indicate that microprofile is included.
Hi @rsoika
Thank you for your fast response.
I am in fact using the Full EE & Web Distribution f 18.0.1.
Said path exists on both 16 and 18.0.1:
Any idea what I am missing?
Just to make sure there are no conflicts with stale deployments. Can you undeploy all existing applications and also check the path
/opt/wildfly/standalone/deployments/
This path should be empty before a new deployment.
Okay so funny enough, using wildfly-19.0.0.Beta3 it just works. I am slightly confused.
Edit: let me try to undeploy all on 18.0.1 and get back to you
In deed this is very confusing because microprofile should be available since version 18.0.0 and we are running many productive applications on wildfly 18. very strange......
By the way: do you have a chance to build your application with docker? This makes live much easier.
Hi @rsoika
I can confirm that I cannot get it to run using 18.0.1, undeloyed everything, cleaned the folder and did a fresh deploy. However WildFly 19 works just fine out of the box. Very weird indeed.
Unfortunately im not able to use docker in this context - ill continue to use WildFly 19, looking forward to when it looses beta though. Feel free to close this issue - if you want to do further investigation we can, but if im the only one experiencing this we can ignore it ;)
Cheers
Only difference I can see is that WF 18 uses microprofile-config-api-1.3.jar while WF 19 uses microprofile-config-api-1.4.jar
Turns out, it was my error trying to reuse standalone.xml of wildfly 13... diffing it seems that wf13 missed "urn:jboss:domain:distributable-web" which causes this weird side effect. sorry for that ... WF18 runs just fine.
Ah! ok now this explains the situation. Yes the standalone.xml file changes form version to version. For that reason I collect them in the docker config folder: https://github.com/imixs/imixs-jsf-example/tree/master/src/docker/configuration/wildfly
OpenLiberty Server is much better in this situation as you can add your own configuration details in an extra project file.
Hi there
I built imixs-jsf-example-5.1.0 with maven as described, and replaced the old 4.0.2 build we had in use. Since microprofile is now used, I had to update WildFly from 13 to the latest stable version 18.0.1. I enabled the microprofile as such
However when deploying the war, I get:
Any ideas what I am missing?
Cheers full log: