Which libraries can be safely packaged in WEB-INF/lib and which not?

[developer251]

Hi all !

we are planning a migration from Tomcat to WildFly: our main concern is that our application bundles lots of libraries into the WEB-INF/lib folder. I've seen in th documentation that in some cases a file jboss-deployment-structure.xml is added to exclude the base server libraries and include those packaged with the applications (e.g. when porting to a different JSF version). In other cases, I've seen that merely packaging the application in the WEB-INF/lib folder overrides the server core modules (e.g. I've tried packaging our Xalan.jar in WEB-INF/lib and it correctly overrides the server core module).

So, is there a guideline of which modules should be migrated using the jboss-deployment-structure.xml and which ones can be safely left in the WEB-INF/lib folder ?

Thanks!

Max

[pmm]

Any JavaEE APIs should neither be in WEB-INF/lib nor in jboss-deployment structure.xml. For what's added automatically check out Implicit module dependencies for deployments - WildFly 8 - Project Documentation Editor. Anything not on that list can either be in jboss-deployment structure.xml (if it's a module) or WEB-INF/lib

[developer251]

Thanks for the clarification!

[ctomc]

Also once you are doing migration, you can just paste list of jars you have in your lib and your jboss-deployment-structure.xml

and we can easier help you out what you could remove from your lib and what not