854375dbcf
The jOOQ 3.12 Open Source Edition will continue to support Java 8. The only things we gain from the JDK 11 dependency is: - Updated logic for reflection when mapping into proxied default methods (that stuff has changed completely in JDK 9). This is a regression, which we can live with. The workaround is to write a custom - Explicit dependency on the JDK 9 API, for which we provide a Java 8 compatible alternative via reactive streams anyway. - JDBC 4.3 compatibility (mostly sharding). We currently don't use that yet. We're not even using internally, outside of a few integration tests. So, we'll postpone the JDK 11 *requirement* (while supporting it nonetheless) to a later release, e.g. 3.13. We'll observe market share shifts. Currently Java 11's market share is a bit of a disappointment, so making it a requirement might be premature. |
||
|---|---|---|
| .. | ||
| src/main | ||
| .gitignore | ||
| LICENSE.txt | ||
| pom.xml | ||
| README.md | ||
Thanks for downloading jOOQ. Please visit http://www.jooq.org for more information.
To install and run this example, simply check it out and run the following Maven command
$ pwd
/path/to/checkout/dir
$ cd jOOQ-examples/jOOQ-javaee-example
...
$ mvn clean install
After the above, you should find a jooq-javaee-example.war file in
$ pwd
/path/to/checkout/dir
$ cd jOOQ-examples/jOOQ-javaee-example/target
...
You can deploy this war file in your WildFly AS or any other application server. The example will use an embedded H2 database, which should be pre-filled with the library example H2 database. It uses a non-managed DataSource, which is configured and consumed directly by the application itself.
For more information about how to setup a WildFly project using EJB, please visit the WildFly Quickstart projects, e.g.: https://github.com/wildfly/quickstart/tree/master/ejb-in-war