We should probably have a wizard or tool for adding persistence
providers also. That is easier with WildFly 8.x but could be easier. I
think that the EAP installer might have a wizard for adding JDBC
drivers, so that is always an option for users.
On 10/08/2014 03:00 PM, Arun Gupta wrote:
I think providing a tool or CLI or directory that covers majority of
the cases would be really useful.
On Wed, Oct 8, 2014 at 5:37 AM, Jesper Pedersen
> On 10/07/2014 03:50 PM, Arun Gupta wrote:
>> What is the recommended way to deploy a JDBC driver to WildFly ?
> Deploying as a module is the recommended way for a number of reasons,
> * JDBC driver is split into multiple JARs that needs to be considered as one
> * JDBC driver needs to be linked with already deployed modules
> * Multiple versions of the 'same' JDBC driver for a vendor (yes, you can
> rename when using deployments/)
> * Native code integration
> So, while having the option to deploy a JDBC driver in a simple way is good,
> it doesn't cover all the cases that are needed in enterprise deployments.
> Best regards,