My guess is it has something to do with your servlet classpath loader. Which servlet engine are you using ?
On Fri, 14 Dec 2018 at 16:04, Rob Sargent <robjsargent@xxxxxxxxx> wrote:
I’m using javax.servlet-api-3.1.0.jarOn Dec 14, 2018, at 2:02 PM, Rob Sargent <robjsargent@xxxxxxxxx> wrote:I too am suspicious. But the vagaries of javax are daunting.On Dec 14, 2018, at 1:30 PM, Dave Cramer <pg@xxxxxxxxxxxxx> wrote:Strange, I wouldn't think so, but then I haven't used a raw servlet for so long I have no idea.On Fri, 14 Dec 2018 at 13:29, Rob Sargent <robjsargent@xxxxxxxxx> wrote:Using java 1.8, postgresql-42.1.4.jar, embedded tomcat 9
It appears to me that I need to make the call "Class.forName("org.postgresql.Driver)" when the entry is in a servlet. Is this expected, within a servlet, or is this just post hoc ergo propter hoc at it finest and I changed something else (wittingly or not). Same code outside of servlet does not need the forced loading of the class and the manual claims it's not need after java 1.6
But if I comment it out, as just now, “No suitable driver found...”. I was days playing with configuration and such think that this very specific error message was telling me my CLASSPATH was wrong.I wonder if I have an old javax installation (which I put in place just recently).
