First, commons-io-2.5.jar of use is to use EAP is PRIVATE of, basically we do not have those customers to use the module.
Below, there is a list for the segregation of each module to knowledge:
A module with private classification is an internal component intended for use exclusively by the JBoss EAP application server. Private module APIs or behavior may change without notice, which can cause instability in applications that use them.
As a workaround, it will be your application on whether correct. For terms of whether it is correct from our company, but comment is difficult, it can be realized If the fact that there, the message itself, which is output if you have ignored, problem I think that those of no level.
Looks like you are telling me that commons jar is private to jboss. I did take a look under modules and do see org.apache.commons listed. So whats the best way to use it? commons-fileupload needs it to work. How do we get the commons-io module to load?
You will need to change org.apache.commons-fileupload module.xml to have also dependency to commons io.In general you should be packaging these with your app rather than relying on the application servers version, as the servers version could be changed or be removed at any point, unless it is explicitly marked as a public module.
There was no module created for commons-fileupload. What we did was copy the jars commons-fileupload-1.3.2.jar and commons-io-2.5.jar to /jboss-eap-7.0/standalone/deployments. They got deployed.
The jboss-deployment-structure.xml then included both jars as the dependency. When the application runs, commons-fileupload is being found ok, so why not commons-io?