Wildfly 17.0.1 - Deletes my JIBX binding classes at server startup

[Shashi Samudrala]

I have a very strange issue. 

I recently switched over from a windows to a Mac, and have been having this problem ever since. I have an EJB, Spring application that i've setup locally, and it uses Wildfly 17.0.1

1. I build my EAR

2. Deploy to the deployments folder of wildfly

3. Start my wildfly server (STS is my IDE, not sure that matters)

At step 1, when I have my EAR, I verify that my jibx binding classes are present within my EAR and are existing where they should be. However, soon after step 3 (startup), even before my console logs start rolling, all of my jibx binding classes disappear from the deployed EAR. Very strange. 

I've tried to move my wildfly home directory around, tried a different version of wildfly, multiple things but cannot seem to resolve this issue.

Could this be a Mac filesystem problem? Or something that wild fly does not like about jibx :) (all of my jibx binding classes are entirely cleaned up)

Please help! Thanks much.

[Paul Ferraro]

I haven't used JiBX in well over 10 years, but I glad to hear the project is alive and well!

From what I recall, JiBX supports both compile and runtime binding.  It sounds like you are expecting the use the former, but runtime binding is kicking in and attempting to re-write your binding classes.

Can you verify that your application does not include jibx-bind.jar?  You would not want to include this unless you are using runtime binding, IIRC.