| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Thanks Gurpreet! Great work! Technically it looks good to me, though I've not been able to run it yet (OJDBC dependency issues..) I'd just like to think through a couple of issues associated with the difficulty of obtaining proprietary Oracle assets for testing and actual use:
Let's talk about these some time. |
Sorry, something went wrong.
|
I've pulled in your override commit into my branch and made the changes to support Oracle. |
Sorry, something went wrong.
|
Hi Gurpreet Please could you refactor your PR into the altered project structure? Please:
|
Sorry, something went wrong.
|
Hi Rich. I've updated the code to reflect the changes requested in your last comment. |
Sorry, something went wrong.
There was a problem hiding this comment.
I imagine the Oracle JDBC driver needs to be added here - please make sure you're using the standard groupId:artifactId for it (can't remember what the convention is off the top of my head)
Sorry, something went wrong.
There was a problem hiding this comment.
Added
Sorry, something went wrong.
There was a problem hiding this comment.
Scope here and for dbutils seems to have changed - should be test, I think!
Sorry, something went wrong.
There was a problem hiding this comment.
Ah - sorry I just noticed: please use plain JDBC for the container liveness check, not Hikari.
Much as I love Hikari and think everyone should use it for their DB connection pooling needs, I'm not quite yet ready to force it upon everybody as a compile-scoped dependency. We should be able to use regular JDBC to do the liveness check.
(NB I know the presence of the zexec library goes against the above philosophy, and I'm mulling replacing it with a JDK-standard approach!)
Sorry, something went wrong.
There was a problem hiding this comment.
Keep the feedback coming!
Sorry, something went wrong.
…leDataSource Changed Hikari Maven Dependency scope to Test No longer exposing Port 22
|
Hmm, attempting to merge this but the Oracle XE container seems to be blowing up. I can't understand how I'd be the first to see this, but it seems that the container has the wrong permissions set on its /var/run/sshd folder: ❯ docker run -p 1521:1521 alexeiled/docker-oracle-xe-11g Starting Oracle Net Listener. Starting Oracle Database 11g Express Edition instance. /var/run/sshd must be owned by root and not group or world-writable. ~/projects/tc git$master 28.9s ❯ I've confirmed that this does seem to be a trait of the container: ❯ docker run -p 1521:1521 -it alexeiled/docker-oracle-xe-11g /bin/bash root@a386c8710f43:/# ls -al /var/run/sshd total 8 drwxr-xr-x 2 oracle dba 4096 Jan 11 2014 . drwxr-xr-x 7 root root 4096 Jan 12 2014 .. root@a386c8710f43:/# exit I'm going to see whether the wnameless fork fares any better; it seems to be much more actively maintained at any rate... |
Sorry, something went wrong.
|
Went with wnameless in the end - @gusohal please confirm whether this is an issue for you. |
Sorry, something went wrong.
|
No problem at all. I didn't seem to have any issues with the original container. Weird. |
Sorry, something went wrong.
…ficates Add configuration setting that allows disabling TLS certificate validation
| Back | FazBrowse Home | New Git URL |
Created an Oracle Container and simple test