I have often though that it would be good to have support in
jboss-modules for directory based resource root (i.e. include all jars
in a directory).
That way we could include a pre-configured module directory that the
user can just dump their drivers in, and we could also include a
pre-configured global module, to make it easy for a user to expose a
library to every deployed application.
Stuart
Arun Gupta wrote:
Including Adam in the loop and here is what he had to say:
-- cut here --
I tried to install either DerbyDB or HSQLDB and they did not had the
META-INF/services/java.sql.Driver file. In such case you will have to
re-create the jar with the property file.
I would expect to just make the JARs available in the CLASSPATH as it
is the case in all other application servers,
-- cut here --
Suggestions ?
Arun
On Tue, Oct 7, 2014 at 1:31 PM, Brian Stansberry
<brian.stansberry(a)redhat.com> wrote:
> You can deploy the driver as a jar, just like a war, ear etc. Then use
> the deployment name in the driver element of the datasource config.
>
>
https://docs.jboss.org/author/display/WFLY9/DataSource+configuration
>
> This old wiki article is pretty good too:
>
>
https://developer.jboss.org/wiki/DataSourceConfigurationInAS7
>
> On 10/7/14, 2:50 PM, Arun Gupta wrote:
>> I was talking to Adam Bien and he is an avid supporter of WildFly and
>> using it in all his projects now. One of his pet peeves is deployment
>> of JDBC driver.
>>
>> He can either bundle it in WEB-INF/lib but prefer to deploy it on the
>> application server itself. Currently he deploys it as a JBoss module
>> but prefer it to be rather simplistic. His suggestion was to define a
>> directory like "standalone/lib/jdbc" and any JAR files copied there
>> should be automatically deployed as module.
>>
>> What is the recommended way to deploy a JDBC driver to WildFly ?
>>
>> Does it necessarily have to be deployed as JBoss module ? If yes, how
>> can this be simplified ?
>>
>> Cheers
>> Arun
>>
>
> --
> Brian Stansberry
> Senior Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev