Probably because deployments are propagated between cluster nodes and modules no. right?
at page 54:
The first and recommened approach consists of installing the driver as a module
In section named installing the driver as a deployment unit we will account for another approach which is usually a bit faster however it has a few limitations.
Next the author say that you will have problems with jdbc 4 non compliant driver using jdbc deployments.
It's better to deploy jdbc as module.
Davide, do you agree that the official documentation is not very clear about that?
I think that the sentence:
If your JDBC driver JAR is not JDBC 4-compliant, it can be made deployable in one of a few ways.
It's little ambiguous because is in the "Installing a JDBC driver as a deployment" section.
Anyway i preferer to install jdbc driver as module because i don't think to change often jdbc driver, i can take a couple of minutes to copy manually the directory without having problems about compliance or not compliance of jdbc driver.