Mail Archive Home | enhydra List | August 2006 Index

migrating to 6.x: cons and pros

Subject: migrating to 6.x: cons and pros
From: Alec Swan <aukcioner@xxxxxxxxx>
Date: Sun, 13 Aug 2006 12:58:20 -0700 (PDT)
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=fmsRkL/TbbCMeyEnv2gsk4vqa5WxVYlf2EWfnFy/dqjetD++MO0NXI92b9PTFHquBhlWp3KUfPUbJUR7f5j587Rm7x6NHt3XhRnNVP3g7kXmLcQAvHHszX14973pLxHR87eK6gp350IGBjVYDXKIsVgP/8Bfwnd7gPCKo8lpJVA= ;

Hi,

My current environment is Fedora Core 3, Enhydra 5.1 (should I switch to 6.1?), JDK 1.4.2 (would like to upgrade to 1.5), Postgres 7.3.4 (would like to upgrade to 8.1), Apache 1.3.1 (would like to upgrade to 2.0).

I just upgraded my database to PostgreSQL 8.1 and now I can't get DODS to work because of the issue described here: http://mail-archive.objectweb.org/enhydra/2005-03/msg00009.html

First, I am wondering if this issue has been fixed in the latest versions of DODS. If yes, then this would give me another reason to upgrade to Enhydra 6.1.

Second, are there a lot of benefits of switching to Enhydra 6.1? How hard is it to migrate from Enhydra 5.1 to 6.x and is it worth the headache? I remember I had to jump through all kinds of hoops to get Enhydra Director to work with apache 1.3. How easy is this integration with Enhydra 6.x release?

Also, I would like to switch to Java 5.0 in all my projects. Will Enhydra 6.x work with Java 5.0?

Thanks.

Alec

migrating to 6.x: cons and pros, Alec Swan
- Re: [enhydra] migrating to 6.x: cons and pros, Slobodan Vujasinovic

<-- Date Index -->

<-- Thread Index -->

Search ObjectWeb Mail Archive:
Advanced Search - Powered by Google