Re: JDBC driver works in ccommand line, not in Tomcat5 - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: JDBC driver works in ccommand line, not in Tomcat5
Date
Msg-id 13178.1189004844@sss.pgh.pa.us
Whole thread Raw
In response to Re: JDBC driver works in ccommand line, not in Tomcat5  (Kris Jurka <books@ejurka.com>)
Responses Re: JDBC driver works in ccommand line, not in Tomcat5
List pgsql-jdbc
Kris Jurka <books@ejurka.com> writes:
> Turns out this is pretty easy to do, I'm just not sure what the best text
> to report to the user is, so far I have:

>      Your security policy has prevented the connection from being
>      attempted.  You must grant the connect java.net.SocketPermission
>      to the database server host and port that you wish to connect to.

Can you really tell for sure that it's security policy and not something
else?  A message as specific as this would be downright
counterproductive if it's wrong.

FWIW, the backend's style guide would suggest dividing that into an
ERROR and a HINT, particularly if the HINT could be mistaken.

            regards, tom lane

pgsql-jdbc by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: PreparedStatement rounds doubles to scale 14 during update
Next
From: Josh Berkus
Date:
Subject: Caching driver on pgFoundry?