-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include Postgres JDBC driver in pom.xml #6819
Comments
The timers are re-using the applications data source. Even complaining about preexisting tables. 🐌
|
… PostgreSQL driver no longer necessary. See IQSS#6819.
… PostgreSQL driver no longer necessary. See IQSS#6819.
This commit is a first test to apply database configuration and credentials to the application server without using a config on domain level but on application level. It is not very configurable yet. The JNDI names have been changed to be conform with Java EE 7. See https://github.com/javaee-samples/javaee7-samples/tree/master/jpa/datasourcedefinition-applicationxml-pu and others for working examples. (Staying with the old name was not successfull.) We had to use the "global" scope, so the persistent EJB timers are successfully created and stored in the database. Using the "app" scope crashes the deployment.
… variables in annotation options. IQSS#6819
any news on this ? |
@xoroz back in July I did a quick test of a pull request by @poikilotherm and left a review here: #7048 (review) There's additional conversation in that pull request. |
…g Payara 5.2020.5+. IQSS#6819
…file on classpath. IQSS#6819
….2.18 from v42.2.12 in the same go. IQSS#6819
…more, as in WAR now. IQSS#6819
Conflicts: pom.xml (payara version .2 vs .6)
(I looked everywhere, but I could not find an existing issue for this, thus creating a new. This is related to my old epic #5292 and had a commit for it, see df2b8cc)
Modern app servers are capable to load the JDBC driver from the deployed WAR when setting up database connections.
This makes manual installation of the Postgres driver obsolete and enables usage during integration tests with Testcontainers.
The addition to
pom.xml
is very simple:In addition, instead of letting the installer configure the database connection indomain.xml
, we can provide the connection details either from annotations (Java EE standard compliant, should be preferred) or provide them fromglassfish-resources.xml
(which also support variables substitution from domain, environment or alias).Note: the above has been skipped as beyond scope for now. Small steps.
Obviously, this affects a lot of places. Docs (#6593), installer (#6761), container images, ...
It makes updating and testing much easier: there is only ONE place to change the version, ideally by using a Maven property.
I already tested this a while ago, see links below.
What I don't remember: it's not clear if the timers database can be used for this, too. IIRC this is why I created #5345...
See also:
The text was updated successfully, but these errors were encountered: