This issue is only applicable to WildFly-Swarm based Teiid when using OData.

OData V4 war file uses the "org.apache.commons.lang" version "3.3.2", however, due to the nature of how Wildfly-Swarm loads the classes it is unable to load the module for the same.

Looks like WildFly-Swarm also makes use of artifacts maven co-ordinates in some fashion from the feature-pack definitions then builds the classpath based on module definition. This is not consistent with WildFly but seems logical. To fix this module definition needs to be updated in Teiid then Teiid version needs to be updated WF-Swaram for OData to work correctly.