datasource

Grails 3 (3.0.9) app is failing to start on a TC server where another 2 Grails 2 apps using each its JNDI datasource are running fine. It seems that replicating my Grails 2 JNDI settings in Grails 3 is not working (I left everything else default and specified driverClassName, dbCreate and jndiName for my prod datasource settings). The application has no problem connecting to the MySQL database straight through JDBC. Only JNDI makes it crash with the below exception (fragment)... ERROR grails.boot.GrailsApp - Application startup failed org.springframework.beans.factory.BeanCreationException:

Context I have a JBoss where I have sucessfully deployed a datasource mydatasource-ds.xml . It's JNDI name is java:mydatasourceDS . JBoss claims that the datasource is succesfully deployed. The JMX console agress too. Problem I want to use this datasource from a client java app launched on a separate JVM. But I get an exception saying the java:mydatasourceDS cannot be found. java.lang.ClassCastException: javax.naming.Reference cannot be cast to javax.sql.DataSource Details Here is the persistence.xml file : <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java

I'm using MyBatis-guice 3.3 to connect to a first database using a java Properties object and a ScriptRunner to run few scripts: Environment environment = injector.getInstance(SqlSessionFactory.class).getConfiguration().getEnvironment(); DataSource source = environment.getDataSource(); ScriptRunner runner = new ScriptRunner(source.getConnection()); runner.setLogWriter(null); runner.setStopOnError(true); runner.runScript(Resources.getResourceAsReader(properties.getProperty("script.dbA.create.schema"))); Now I would like to add a second datasource (dbB) using the same approach. Following the

I would like to bind DataSource object to (eclipse) jetty's JNDI context programatically. I need for testing purpose. Here's a piece of code I have now: server = new Server(SERVER_PORT); webAppContext = new WebAppContext(); webAppContext.setResourceBase("."); webAppContext.setContextPath("/" + SERVER_CONTEXT); webAppContext.addEventListener(prepareServletContextListener()); webAppContext.addFilter(GuiceFilter.class, "/*", null); webAppContext.addServlet(DefaultServlet.class, "/"); Resource r = new Resource(webAppContext,"jdbc/testDS",createDataSource()); server.setHandler(webAppContext);

I'm getting an error on my reportviewer which I am not sure how to correct this.... The error that I am gettings is : " A data source instance has not been supplied for the data source 'Request'." I have tried searching for this, but can't find anything that I can see that is wrong, can somebody please point me in the right direction? This is how my reportvierer looks like: <rsweb:ReportViewer ID="rptViewer" runat="server" Height="654px" Width="924px" Font-Names="Verdana" Font-Size="8pt" InteractiveDeviceInfos="(Collection)" WaitMessageFont-Names="Verdana" WaitMessageFont-Size="14pt">

I am configuring a mysql connection in an application server (glassfish specifically, but I am curious about other application servers as well) and it appears that there are 2 extremely similar options for the resource type & driver. Namely, MysqlDataSource and MysqlConnectionPoolDataSource . I am curious about what the difference between the two is. It appears that glassfish is maintaining a connection pool either way, so it's difficult to tell what the difference is. Thanks for any insight that you can provide. MysqlDataSource is a Java Native Database Interface that returns a connection to

I can´t configure my datasource by using a "*-ds.xml" deployment descriptor with the database driver installed as module. The datasource *-ds.xml file is only valid if I deploy the database driver directly as jar. I think that If you choose to install the driver as a module you will have to configure the datasource in the standalone.xml directly. I would like the solution driver module + deployment descriptor. eis For your module to be visible to your application, you need to import the module to your application. You need jboss-deployment-structure.xml in your WEB-INF for your application,