While I realize we need to get a real solution out it seems rather poor of jTDS to not support the JDBC4 spec with a JDK6 driver since the JDBC4 spec was _part of_ the JDK6 release.
Hibernate 4.1.7, 4.1.8, and 4.1.9 all contain patches for the NaturalID feature that uPortal 4.0 is using heavily and can be affected by in some cases. I'd be strongly opposed to rolling back the hibernate dependency and potentially introducing bugs that would affect everyone due to jTDS's poor API tracking.
Honestly I'd get start a thread with jTDS and then cross-post it to the uportal-user email list encouraging everyone that uses MSSQL to chime in. Its rather poor form that they don't support a JDBC API that has existed since day one in Java 6 (as far as I can tell anyways)
-Eric On 1/11/13 2:37 PM, Drew Wills wrote:
Hey folks,Kostya at SCSU brought an issue to my attention that I think is worth noting...It seems that -- starting with v4.1.7 -- Hibernate requires JDBC4 support:- https://hibernate.onjira.com/browse/HHH-7778 But the jTDS driver is targeting JDBC4 for their 1.3 line:- http://sourceforge.net/p/jtds/news/2012/10/jtds-jdbc-driver-127-and-130-released/JTDS is a popular 3rd-party driver for MS SQL Server.The issue is that 1.3 also (apparently) _requires_ Java 7. I know there has been much recent work to support Java 7... where are we on that? Is that (as I seem to remember) a uP 4.1 only thing?The uP4 manual still says Java 7 not supported: - https://wiki.jasig.org/display/UPM40/RequirementsI have suggested that _perhaps_ rolling the version of hibernate back (from 4.1.9 currently) to 4.1.6 would allow the most recent jTDS 1.2 driver to work.drew
smime.p7s
Description: S/MIME Cryptographic Signature
