I will plan some migration tests since ODE does object serialization. Our last release was ODE 1.3.6, but will use a version older to that which is ODE 1.3.5
Initial setup: ODE war: ODE 1.3.5 Tomcat 6.0.44 JDK 1.5.0_22 Deploy some processes (sample processes that come packaged with ODE distribution and a custom process that uses explicit correlation) and initiate instances. Migration setup: ODE war: Replace ODE 1.3.5 deployed previously with ODE 1.3.7-SNAPSHOT built with minimum binary compatibility to JDK 6 Tomcat 6.0.44 JDK 1.6.0_45 Now complete pending process instances and create new instances. Will come back with the migration test results. regards, sathwik On Mon, Nov 30, 2015 at 1:35 AM, Kevin SEJOURNE < [email protected]> wrote: > Hello, > > Why wait for jdk8 ? > +1 for moving for a newer version. > > Regards, > Kevin > > > Kevin SEJOURNE > Ingénieur Recherche et Développement > Standard : +33141917777 | Fax : +33141917778 > 215, avenue Georges Clemenceau - 92024 - Nanterre > www.intrinsec.com > > ________________________________________ > De : Hadrian Zbarcea <[email protected]> > Envoyé : samedi 28 novembre 2015 13:55 > À : [email protected] > Objet : [!!Mass Mail]Re: Move towards binary compatibility to JDK 1.6 or > JDK 1.7 for 1.3.7 RELEASE > > +1 for moving to either jdk7 (safer bet) or even jdk8. > > Hadrian > > On 11/27/2015 06:19 PM, Tammo van Lessen wrote: > > +1 for moving to JDK 7 (although its also already EOL), so JDK 8 would > also > > be an option if nobody objects. > > > > On Fri, Nov 27, 2015 at 7:57 AM, Sathwik B P <[email protected]> > wrote: > > > >> Hi All, > >> > >> This is a proposal to move towards minimum compliance to JDK 1.6 or 1.7 > >> from existing JDK 1.5 for ODE 1.3.7 RELEASE. > >> > >> Is there anyone still on JDK 5 or 6? Let us know if there are any > concerns. > >> > >> regards, > >> sathwik > >> > > > > > > > > > > > > > >
