This is a new release of Hibernate we are talking about. If we go with JDK 1.6
support in 3.6 and people cannot use it in WAS because of this fact they can still use
3.5.
-- Sent from my Palm Pre
steve(a)hibernate.org
http://hibernate.orgOn Apr 9, 2010 9:47 AM, Tomasz Blachowicz
<tblachowicz(a)gmail.com> wrote:
Hi Steve,
One environment that stings into my mind is WAS 6.1. This version of WebSphere AS is very
popular ans still largely used, especially on mainframe platform. I came
across WAS 6.1 when working with a few customers. As far as I know WAS 6.1 foes not
have support for 1.6, so that would block Hibernate upgrade path for all
the applications targeted for this environment and that would be regret.
Regards,Tom
On Fri, Apr 9, 2010 at 2:49 PM, Steve Ebersole <steve(a)hibernate.org> wrote:
One item scheduled for 3.6 is dropping JDK 1.4 support. Which leaves
the question of whether to go 1.5 or 1.6. I know 1.5 is within its EOL,
but I dont think that should be the deciding factor.
Really I was more thinking of JDBC differences and (1) not having to
maintain different JDBC 3 and JDBC 4 code and (2) leveraging some JDBC 4
features. TO me the big question comes down to what environments do we
know that do not support JDK 1.6
Another option is to make the intermediate jump to 1.5 since I will not
be making the changes that would require compile time dep on 1.6 in our 3.6.
But at any rate, I'd like to understand the environments which currently
do not support 1.6.
--
steve(a)hibernate.org
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev