You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Sathwik B P <sa...@gmail.com> on 2015/11/27 07:57:05 UTC
Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
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
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
I do agree with your point, there were customers in the past who wanted the
GA branch on jdk 8, but could not because of the problem explained earlier.
By moving to jdk 1.6, we would expand the horizon of adoption.
On Nov 28, 2015 4:09 PM, "Pierre Smits" <pi...@gmail.com> wrote:
> Trunk is to volatile to be used for adoption (by end users, meaning end
> users and contributors not necessarily being the same). Hence the
> standpoint of the ASF of making releases available.
>
> Mixing compatibility aspects regarding jdk 6,7 and 8 in one release branch
> is undesirable from a communication standpoint of view. It is better
> (easier) to communicate that 1.3 is jdk 7 compatible and the next release
> branch is not, than 1.3 is jdk 6, jdk 7 and jdk 8 compatible depending on
> the version picked.
>
> Best regards,
>
> Pierre Smits
>
> *OFBiz Extensions Marketplace*
> http://oem.ofbizci.net/oci-2/
>
> On Sat, Nov 28, 2015 at 11:19 AM, Sathwik B P <sa...@gmail.com>
> wrote:
>
> > Pierre,
> >
> > Trunk is already tagged as 1.4. It is already compilable on jdk 8. We
> need
> > to test it a bit more.
> >
> > We need to bring adopters in sync with the trunk as soon as possible and
> > this is the first step to sync release branch and trunk.
> > On Nov 28, 2015 3:34 PM, "Pierre Smits" <pi...@gmail.com> wrote:
> >
> > > May I suggest (given the ODE-1.3.x branch not being jdk 8 compatible)
> to
> > > leave branch 1.3.x as is, and create a new branch (1.4?) to have that
> > > become fully jdk 8 compatible.... Both code and annotation wise.
> > >
> > > That would help sending a clear message to both community and potential
> > > adopters.
> > >
> > > Best regards,
> > >
> > >
> > > Pierre Smits
> > >
> > > *OFBiz Extensions Marketplace*
> > > http://oem.ofbizci.net/oci-2/
> > >
> > > On Sat, Nov 28, 2015 at 10:52 AM, Sathwik B P <sa...@gmail.com>
> > > wrote:
> > >
> > > > Hi pierre,
> > > > I am doing good. Thank you.
> > > > How's business process discussion going on. If you need us let us
> know.
> > > >
> > > > Moving to higher jdk has been sitting from long time. The reason i
> have
> > > > brought this issue is because of the use of legacy Annotations Api
> > which
> > > > has been removed in jdk 8.
> > > >
> > > > ODE source code current release branch ODE-1.3.x is non compilable on
> > jdk
> > > > 8.
> > > >
> > > > The new Annotation Api is available in jdk 1.6,1.7
> > > >
> > > > TRUNK branch is compilable on jdk 8 as as we have a completly new
> Jacob
> > > > implementation.
> > > >
> > > > I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait
> for
> > > > responses from the commmunity
> > > > On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com>
> > > 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 <sathwik.bp@gmail.com
> >
> > > > 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
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Tammo van Lessen - http://www.taval.de
> > > > >
> > > >
> > >
> >
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Pierre Smits <pi...@gmail.com>.
Trunk is to volatile to be used for adoption (by end users, meaning end
users and contributors not necessarily being the same). Hence the
standpoint of the ASF of making releases available.
Mixing compatibility aspects regarding jdk 6,7 and 8 in one release branch
is undesirable from a communication standpoint of view. It is better
(easier) to communicate that 1.3 is jdk 7 compatible and the next release
branch is not, than 1.3 is jdk 6, jdk 7 and jdk 8 compatible depending on
the version picked.
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Sat, Nov 28, 2015 at 11:19 AM, Sathwik B P <sa...@gmail.com> wrote:
> Pierre,
>
> Trunk is already tagged as 1.4. It is already compilable on jdk 8. We need
> to test it a bit more.
>
> We need to bring adopters in sync with the trunk as soon as possible and
> this is the first step to sync release branch and trunk.
> On Nov 28, 2015 3:34 PM, "Pierre Smits" <pi...@gmail.com> wrote:
>
> > May I suggest (given the ODE-1.3.x branch not being jdk 8 compatible) to
> > leave branch 1.3.x as is, and create a new branch (1.4?) to have that
> > become fully jdk 8 compatible.... Both code and annotation wise.
> >
> > That would help sending a clear message to both community and potential
> > adopters.
> >
> > Best regards,
> >
> >
> > Pierre Smits
> >
> > *OFBiz Extensions Marketplace*
> > http://oem.ofbizci.net/oci-2/
> >
> > On Sat, Nov 28, 2015 at 10:52 AM, Sathwik B P <sa...@gmail.com>
> > wrote:
> >
> > > Hi pierre,
> > > I am doing good. Thank you.
> > > How's business process discussion going on. If you need us let us know.
> > >
> > > Moving to higher jdk has been sitting from long time. The reason i have
> > > brought this issue is because of the use of legacy Annotations Api
> which
> > > has been removed in jdk 8.
> > >
> > > ODE source code current release branch ODE-1.3.x is non compilable on
> jdk
> > > 8.
> > >
> > > The new Annotation Api is available in jdk 1.6,1.7
> > >
> > > TRUNK branch is compilable on jdk 8 as as we have a completly new Jacob
> > > implementation.
> > >
> > > I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait for
> > > responses from the commmunity
> > > On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com>
> > 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 <sa...@gmail.com>
> > > 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
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Tammo van Lessen - http://www.taval.de
> > > >
> > >
> >
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Pierre,
Trunk is already tagged as 1.4. It is already compilable on jdk 8. We need
to test it a bit more.
We need to bring adopters in sync with the trunk as soon as possible and
this is the first step to sync release branch and trunk.
On Nov 28, 2015 3:34 PM, "Pierre Smits" <pi...@gmail.com> wrote:
> May I suggest (given the ODE-1.3.x branch not being jdk 8 compatible) to
> leave branch 1.3.x as is, and create a new branch (1.4?) to have that
> become fully jdk 8 compatible.... Both code and annotation wise.
>
> That would help sending a clear message to both community and potential
> adopters.
>
> Best regards,
>
>
> Pierre Smits
>
> *OFBiz Extensions Marketplace*
> http://oem.ofbizci.net/oci-2/
>
> On Sat, Nov 28, 2015 at 10:52 AM, Sathwik B P <sa...@gmail.com>
> wrote:
>
> > Hi pierre,
> > I am doing good. Thank you.
> > How's business process discussion going on. If you need us let us know.
> >
> > Moving to higher jdk has been sitting from long time. The reason i have
> > brought this issue is because of the use of legacy Annotations Api which
> > has been removed in jdk 8.
> >
> > ODE source code current release branch ODE-1.3.x is non compilable on jdk
> > 8.
> >
> > The new Annotation Api is available in jdk 1.6,1.7
> >
> > TRUNK branch is compilable on jdk 8 as as we have a completly new Jacob
> > implementation.
> >
> > I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait for
> > responses from the commmunity
> > On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com>
> 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 <sa...@gmail.com>
> > 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
> > > >
> > >
> > >
> > >
> > > --
> > > Tammo van Lessen - http://www.taval.de
> > >
> >
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Pierre Smits <pi...@gmail.com>.
May I suggest (given the ODE-1.3.x branch not being jdk 8 compatible) to
leave branch 1.3.x as is, and create a new branch (1.4?) to have that
become fully jdk 8 compatible.... Both code and annotation wise.
That would help sending a clear message to both community and potential
adopters.
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Sat, Nov 28, 2015 at 10:52 AM, Sathwik B P <sa...@gmail.com> wrote:
> Hi pierre,
> I am doing good. Thank you.
> How's business process discussion going on. If you need us let us know.
>
> Moving to higher jdk has been sitting from long time. The reason i have
> brought this issue is because of the use of legacy Annotations Api which
> has been removed in jdk 8.
>
> ODE source code current release branch ODE-1.3.x is non compilable on jdk
> 8.
>
> The new Annotation Api is available in jdk 1.6,1.7
>
> TRUNK branch is compilable on jdk 8 as as we have a completly new Jacob
> implementation.
>
> I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait for
> responses from the commmunity
> On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com> 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 <sa...@gmail.com>
> 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
> > >
> >
> >
> >
> > --
> > Tammo van Lessen - http://www.taval.de
> >
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Hi Tammo,
As i have indicated we need to migrate to new Annotation Api, which is
required only for our release branch Ode-1.3.x
Can you build a new docker image based on jdk 8.
We might as well discuss and make ODE 1.3.7 as the last maintanance release
from 1.3.x and then move to the trunk for future releases.
Regards,
Sathwik
On Nov 28, 2015 3:22 PM, "Sathwik B P" <sa...@gmail.com> wrote:
> Hi pierre,
> I am doing good. Thank you.
> How's business process discussion going on. If you need us let us know.
>
> Moving to higher jdk has been sitting from long time. The reason i have
> brought this issue is because of the use of legacy Annotations Api which
> has been removed in jdk 8.
>
> ODE source code current release branch ODE-1.3.x is non compilable on jdk
> 8.
>
> The new Annotation Api is available in jdk 1.6,1.7
>
> TRUNK branch is compilable on jdk 8 as as we have a completly new Jacob
> implementation.
>
> I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait for
> responses from the commmunity
> On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com> 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 <sa...@gmail.com>
>> 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
>> >
>>
>>
>>
>> --
>> Tammo van Lessen - http://www.taval.de
>>
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Hi Tammo,
As i have indicated we need to migrate to new Annotation Api, which is
required only for our release branch Ode-1.3.x
Can you build a new docker image based on jdk 8.
We might as well discuss and make ODE 1.3.7 as the last maintanance release
from 1.3.x and then move to the trunk for future releases.
Regards,
Sathwik
On Nov 28, 2015 3:22 PM, "Sathwik B P" <sa...@gmail.com> wrote:
> Hi pierre,
> I am doing good. Thank you.
> How's business process discussion going on. If you need us let us know.
>
> Moving to higher jdk has been sitting from long time. The reason i have
> brought this issue is because of the use of legacy Annotations Api which
> has been removed in jdk 8.
>
> ODE source code current release branch ODE-1.3.x is non compilable on jdk
> 8.
>
> The new Annotation Api is available in jdk 1.6,1.7
>
> TRUNK branch is compilable on jdk 8 as as we have a completly new Jacob
> implementation.
>
> I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait for
> responses from the commmunity
> On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com> 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 <sa...@gmail.com>
>> 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
>> >
>>
>>
>>
>> --
>> Tammo van Lessen - http://www.taval.de
>>
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Hi pierre,
I am doing good. Thank you.
How's business process discussion going on. If you need us let us know.
Moving to higher jdk has been sitting from long time. The reason i have
brought this issue is because of the use of legacy Annotations Api which
has been removed in jdk 8.
ODE source code current release branch ODE-1.3.x is non compilable on jdk 8.
The new Annotation Api is available in jdk 1.6,1.7
TRUNK branch is compilable on jdk 8 as as we have a completly new Jacob
implementation.
I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait for
responses from the commmunity
On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com> 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 <sa...@gmail.com> 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
> >
>
>
>
> --
> Tammo van Lessen - http://www.taval.de
>
Re: [!!Mass Mail]Re: Move towards binary compatibility to JDK 1.6 or
JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Pierre,
Am aware of the JDK 7 EOF. I wanted to move to 13.7 to JDK 7 and trunk(1.4)
to JDK 8.
I probably missed to post my findings. Currently there are problems in the
Persistence libraries. We have dual ORM implementations OpenJPA and
Hibernate.
Implementation is based on JPA 1.0. OpenJPA's (version 1.2.3) byte code
enhancers are not compatible with JDK 7. That has been fixed in OpenJPA 2.2
which is on JPA 2.0.
On the hibernate side, we use XDoclet annotations to generate HBM files.
The generated HBM files use xml namespaces which are deprecated in JPA 2
version of Hibernate implementation.We will have to replace XDocklet
annotations with either JPA 2 annotations or Hibernate annotations.
That would entice us to upgrade to JPA 2.
https://issues.apache.org/jira/browse/ODE-1042
This involves quite a bit of work and a lot of testing. I don't think we
can bring that in ODE 1.3.7 release.
Simultaneously we will have to move both the ORM implementations towards
JPA 2.0. It would be great if the community can lend an helping hand :)
regards,
sathwik
On Sun, Dec 20, 2015 at 9:38 PM, Pierre Smits <pi...@gmail.com>
wrote:
> FYI: Java 7 is EOL since April 2015
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Tue, Dec 8, 2015 at 9:30 AM, Sathwik B P <sa...@gmail.com> wrote:
>
> > I wish to confirm that the migration has worked.
> >
> > Initial setup:
> > ODE war: ODE 1.3.5 with Hibernate 3.2.5
> > Tomcat 6.0.44 with Bitronix TM 2.1.4
> > JDK 1.5.0_22
> > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
> >
> >
> > Migration setup:
> > ODE war: ODE 1.3.7-SNAPSHOT built with minimum binary compatibility to
> > JDK 6 with Hibernate 3.3.2
> > TomEE 1.7.12
> > JDK 1.7.0_80
> > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
> >
> > We can now move release ODE 1.3.7 with binary compatibility to JDK 6.
> >
> >
> > regards,
> > sathwik
> >
> > On Sun, Dec 6, 2015 at 7:51 PM, Sathwik B P <sa...@gmail.com>
> wrote:
> >
> > > Hi,
> > >
> > > As of now I have faced two issues with the compiling of ODE-1.3.x
> source
> > > after changing the binary compatibility to 1.6
> > >
> > > A) With the removal of usage of APT tool in Rakefile. How do we
> generate
> > > the Channel and ChannelListener sources. There were 2 options
> > > 1) Rewrite the annotation processor using new API
> > > 2) Manually add the generated sources to the repo which was
> generated
> > > with JDK 1.5
> > >
> > > Since we don't use the annotations API in the trunk anymore, I choose
> to
> > > manually add the generated source to the repo.
> > >
> > >
> > > B) XMLBeans, for multiple occurrence element defined in XSD schema
> > > generates different methods under JDK 1.5 and JDK 1.6
> > >
> > > Collection<Something> getSomethingList() -----JDK 1.5
> > > Something[] getSomethingArray() ----- JDK 1.6
> > >
> > > The generated sources from XMLBeans is predominantly used in the
> > > Management API within ODE. So, I assume the dependency on this API by
> > > external customers would be rare as they would be entitled to use the
> > WSDL
> > > and XSD.
> > >
> > > These are the following changes that have resulted due to the changes
> in
> > > the XMLBeans generated sources that has gone into trunk and the same
> > needs
> > > to be backported to ode 1.3.7 to make it work on JDK 1.6
> > >
> > >
> >
> https://github.com/apache/ode/commit/ad45177f76a4a7518cb3f79d76e52f55cb86a9c6
> > >
> > >
> > > regards,
> > > sathwik
> > >
> > >
> > > On Wed, Dec 2, 2015 at 2:58 PM, Sathwik B P <sa...@gmail.com>
> > wrote:
> > >
> > >> 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 <
> > >> Kevin.SEJOURNE@intrinsec.com> 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 <hz...@gmail.com>
> > >>> Envoyé : samedi 28 novembre 2015 13:55
> > >>> À : user@ode.apache.org
> > >>> 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 <sathwik.bp@gmail.com
> >
> > >>> 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
> > >>> >>
> > >>> >
> > >>> >
> > >>> >
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >
> >
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Ah, the problem with source and binary compatibility set to JDK 7 is here
https://issues.apache.org/jira/browse/ODE-1043
On Mon, Dec 21, 2015 at 10:02 AM, Sathwik B P <sa...@gmail.com> wrote:
> Raghavendra,
>
> I don't think there should be any problems running ODE binary under JDK 8.
>
> It's only that you will not be able to compile the source under JDK 7 and
> above with source and target version set to JDK 7.I have listed in my
> previous post where we need to move towards JPA 2 to fix that.
>
> It would be of great help if you could test on JDK 8 and let us know, so
> that we can try to fix that in the trunk.
>
> regards,
> sathwik
>
> On Sun, Dec 20, 2015 at 11:08 PM, Raghvendra Srivastava <
> raghvendrasrivastava@gmail.com> wrote:
>
>> Sathwik,
>> As you know we are using ode in our application and we need to move to
>> java8 for compliance and security reasons. Many of our customers are
>> asking
>> us to move our applications to java8. I was wondering what are the plans
>> for porting ode to Java 8 given that Java 7 has also reached EOL few
>> months
>> back?
>> Best regards,
>> Rag
>>
>> On Sunday, December 20, 2015, Pierre Smits <pi...@gmail.com>
>> wrote:
>>
>> > FYI: Java 7 is EOL since April 2015
>> >
>> > Best regards,
>> >
>> > Pierre Smits
>> >
>> > ORRTIZ.COM <http://www.orrtiz.com>
>> > OFBiz based solutions & services
>> >
>> > OFBiz Extensions Marketplace
>> > http://oem.ofbizci.net/oci-2/
>> >
>> > On Tue, Dec 8, 2015 at 9:30 AM, Sathwik B P <sathwik.bp@gmail.com
>> > <javascript:;>> wrote:
>> >
>> > > I wish to confirm that the migration has worked.
>> > >
>> > > Initial setup:
>> > > ODE war: ODE 1.3.5 with Hibernate 3.2.5
>> > > Tomcat 6.0.44 with Bitronix TM 2.1.4
>> > > JDK 1.5.0_22
>> > > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
>> > >
>> > >
>> > > Migration setup:
>> > > ODE war: ODE 1.3.7-SNAPSHOT built with minimum binary compatibility
>> to
>> > > JDK 6 with Hibernate 3.3.2
>> > > TomEE 1.7.12
>> > > JDK 1.7.0_80
>> > > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
>> > >
>> > > We can now move release ODE 1.3.7 with binary compatibility to JDK 6.
>> > >
>> > >
>> > > regards,
>> > > sathwik
>> > >
>> > > On Sun, Dec 6, 2015 at 7:51 PM, Sathwik B P <sathwik.bp@gmail.com
>> > <javascript:;>> wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > As of now I have faced two issues with the compiling of ODE-1.3.x
>> > source
>> > > > after changing the binary compatibility to 1.6
>> > > >
>> > > > A) With the removal of usage of APT tool in Rakefile. How do we
>> > generate
>> > > > the Channel and ChannelListener sources. There were 2 options
>> > > > 1) Rewrite the annotation processor using new API
>> > > > 2) Manually add the generated sources to the repo which was
>> > generated
>> > > > with JDK 1.5
>> > > >
>> > > > Since we don't use the annotations API in the trunk anymore, I
>> choose
>> > to
>> > > > manually add the generated source to the repo.
>> > > >
>> > > >
>> > > > B) XMLBeans, for multiple occurrence element defined in XSD schema
>> > > > generates different methods under JDK 1.5 and JDK 1.6
>> > > >
>> > > > Collection<Something> getSomethingList() -----JDK 1.5
>> > > > Something[] getSomethingArray() ----- JDK 1.6
>> > > >
>> > > > The generated sources from XMLBeans is predominantly used in the
>> > > > Management API within ODE. So, I assume the dependency on this API
>> by
>> > > > external customers would be rare as they would be entitled to use
>> the
>> > > WSDL
>> > > > and XSD.
>> > > >
>> > > > These are the following changes that have resulted due to the
>> changes
>> > in
>> > > > the XMLBeans generated sources that has gone into trunk and the same
>> > > needs
>> > > > to be backported to ode 1.3.7 to make it work on JDK 1.6
>> > > >
>> > > >
>> > >
>> >
>> https://github.com/apache/ode/commit/ad45177f76a4a7518cb3f79d76e52f55cb86a9c6
>> > > >
>> > > >
>> > > > regards,
>> > > > sathwik
>> > > >
>> > > >
>> > > > On Wed, Dec 2, 2015 at 2:58 PM, Sathwik B P <sathwik.bp@gmail.com
>> > <javascript:;>>
>> > > wrote:
>> > > >
>> > > >> 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 <
>> > > >> Kevin.SEJOURNE@intrinsec.com <javascript:;>> 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 <hzbarcea@gmail.com <javascript:;>>
>> > > >>> Envoyé : samedi 28 novembre 2015 13:55
>> > > >>> À : user@ode.apache.org <javascript:;>
>> > > >>> 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 <
>> sathwik.bp@gmail.com
>> > <javascript:;>>
>> > > >>> 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
>> > > >>> >>
>> > > >>> >
>> > > >>> >
>> > > >>> >
>> > > >>>
>> > > >>>
>> > > >>>
>> > > >>>
>> > > >>>
>> > > >>>
>> > > >>>
>> > > >>>
>> > > >>
>> > > >
>> > >
>> >
>>
>
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Raghavendra,
I don't think there should be any problems running ODE binary under JDK 8.
It's only that you will not be able to compile the source under JDK 7 and
above with source and target version set to JDK 7.I have listed in my
previous post where we need to move towards JPA 2 to fix that.
It would be of great help if you could test on JDK 8 and let us know, so
that we can try to fix that in the trunk.
regards,
sathwik
On Sun, Dec 20, 2015 at 11:08 PM, Raghvendra Srivastava <
raghvendrasrivastava@gmail.com> wrote:
> Sathwik,
> As you know we are using ode in our application and we need to move to
> java8 for compliance and security reasons. Many of our customers are asking
> us to move our applications to java8. I was wondering what are the plans
> for porting ode to Java 8 given that Java 7 has also reached EOL few months
> back?
> Best regards,
> Rag
>
> On Sunday, December 20, 2015, Pierre Smits <pi...@gmail.com> wrote:
>
> > FYI: Java 7 is EOL since April 2015
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM <http://www.orrtiz.com>
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Tue, Dec 8, 2015 at 9:30 AM, Sathwik B P <sathwik.bp@gmail.com
> > <javascript:;>> wrote:
> >
> > > I wish to confirm that the migration has worked.
> > >
> > > Initial setup:
> > > ODE war: ODE 1.3.5 with Hibernate 3.2.5
> > > Tomcat 6.0.44 with Bitronix TM 2.1.4
> > > JDK 1.5.0_22
> > > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
> > >
> > >
> > > Migration setup:
> > > ODE war: ODE 1.3.7-SNAPSHOT built with minimum binary compatibility
> to
> > > JDK 6 with Hibernate 3.3.2
> > > TomEE 1.7.12
> > > JDK 1.7.0_80
> > > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
> > >
> > > We can now move release ODE 1.3.7 with binary compatibility to JDK 6.
> > >
> > >
> > > regards,
> > > sathwik
> > >
> > > On Sun, Dec 6, 2015 at 7:51 PM, Sathwik B P <sathwik.bp@gmail.com
> > <javascript:;>> wrote:
> > >
> > > > Hi,
> > > >
> > > > As of now I have faced two issues with the compiling of ODE-1.3.x
> > source
> > > > after changing the binary compatibility to 1.6
> > > >
> > > > A) With the removal of usage of APT tool in Rakefile. How do we
> > generate
> > > > the Channel and ChannelListener sources. There were 2 options
> > > > 1) Rewrite the annotation processor using new API
> > > > 2) Manually add the generated sources to the repo which was
> > generated
> > > > with JDK 1.5
> > > >
> > > > Since we don't use the annotations API in the trunk anymore, I choose
> > to
> > > > manually add the generated source to the repo.
> > > >
> > > >
> > > > B) XMLBeans, for multiple occurrence element defined in XSD schema
> > > > generates different methods under JDK 1.5 and JDK 1.6
> > > >
> > > > Collection<Something> getSomethingList() -----JDK 1.5
> > > > Something[] getSomethingArray() ----- JDK 1.6
> > > >
> > > > The generated sources from XMLBeans is predominantly used in the
> > > > Management API within ODE. So, I assume the dependency on this API by
> > > > external customers would be rare as they would be entitled to use the
> > > WSDL
> > > > and XSD.
> > > >
> > > > These are the following changes that have resulted due to the changes
> > in
> > > > the XMLBeans generated sources that has gone into trunk and the same
> > > needs
> > > > to be backported to ode 1.3.7 to make it work on JDK 1.6
> > > >
> > > >
> > >
> >
> https://github.com/apache/ode/commit/ad45177f76a4a7518cb3f79d76e52f55cb86a9c6
> > > >
> > > >
> > > > regards,
> > > > sathwik
> > > >
> > > >
> > > > On Wed, Dec 2, 2015 at 2:58 PM, Sathwik B P <sathwik.bp@gmail.com
> > <javascript:;>>
> > > wrote:
> > > >
> > > >> 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 <
> > > >> Kevin.SEJOURNE@intrinsec.com <javascript:;>> 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 <hzbarcea@gmail.com <javascript:;>>
> > > >>> Envoyé : samedi 28 novembre 2015 13:55
> > > >>> À : user@ode.apache.org <javascript:;>
> > > >>> 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 <
> sathwik.bp@gmail.com
> > <javascript:;>>
> > > >>> 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
> > > >>> >>
> > > >>> >
> > > >>> >
> > > >>> >
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >
> > >
> >
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Raghvendra Srivastava <ra...@gmail.com>.
Sathwik,
As you know we are using ode in our application and we need to move to
java8 for compliance and security reasons. Many of our customers are asking
us to move our applications to java8. I was wondering what are the plans
for porting ode to Java 8 given that Java 7 has also reached EOL few months
back?
Best regards,
Rag
On Sunday, December 20, 2015, Pierre Smits <pi...@gmail.com> wrote:
> FYI: Java 7 is EOL since April 2015
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Tue, Dec 8, 2015 at 9:30 AM, Sathwik B P <sathwik.bp@gmail.com
> <javascript:;>> wrote:
>
> > I wish to confirm that the migration has worked.
> >
> > Initial setup:
> > ODE war: ODE 1.3.5 with Hibernate 3.2.5
> > Tomcat 6.0.44 with Bitronix TM 2.1.4
> > JDK 1.5.0_22
> > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
> >
> >
> > Migration setup:
> > ODE war: ODE 1.3.7-SNAPSHOT built with minimum binary compatibility to
> > JDK 6 with Hibernate 3.3.2
> > TomEE 1.7.12
> > JDK 1.7.0_80
> > Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
> >
> > We can now move release ODE 1.3.7 with binary compatibility to JDK 6.
> >
> >
> > regards,
> > sathwik
> >
> > On Sun, Dec 6, 2015 at 7:51 PM, Sathwik B P <sathwik.bp@gmail.com
> <javascript:;>> wrote:
> >
> > > Hi,
> > >
> > > As of now I have faced two issues with the compiling of ODE-1.3.x
> source
> > > after changing the binary compatibility to 1.6
> > >
> > > A) With the removal of usage of APT tool in Rakefile. How do we
> generate
> > > the Channel and ChannelListener sources. There were 2 options
> > > 1) Rewrite the annotation processor using new API
> > > 2) Manually add the generated sources to the repo which was
> generated
> > > with JDK 1.5
> > >
> > > Since we don't use the annotations API in the trunk anymore, I choose
> to
> > > manually add the generated source to the repo.
> > >
> > >
> > > B) XMLBeans, for multiple occurrence element defined in XSD schema
> > > generates different methods under JDK 1.5 and JDK 1.6
> > >
> > > Collection<Something> getSomethingList() -----JDK 1.5
> > > Something[] getSomethingArray() ----- JDK 1.6
> > >
> > > The generated sources from XMLBeans is predominantly used in the
> > > Management API within ODE. So, I assume the dependency on this API by
> > > external customers would be rare as they would be entitled to use the
> > WSDL
> > > and XSD.
> > >
> > > These are the following changes that have resulted due to the changes
> in
> > > the XMLBeans generated sources that has gone into trunk and the same
> > needs
> > > to be backported to ode 1.3.7 to make it work on JDK 1.6
> > >
> > >
> >
> https://github.com/apache/ode/commit/ad45177f76a4a7518cb3f79d76e52f55cb86a9c6
> > >
> > >
> > > regards,
> > > sathwik
> > >
> > >
> > > On Wed, Dec 2, 2015 at 2:58 PM, Sathwik B P <sathwik.bp@gmail.com
> <javascript:;>>
> > wrote:
> > >
> > >> 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 <
> > >> Kevin.SEJOURNE@intrinsec.com <javascript:;>> 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 <hzbarcea@gmail.com <javascript:;>>
> > >>> Envoyé : samedi 28 novembre 2015 13:55
> > >>> À : user@ode.apache.org <javascript:;>
> > >>> 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 <sathwik.bp@gmail.com
> <javascript:;>>
> > >>> 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
> > >>> >>
> > >>> >
> > >>> >
> > >>> >
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >
> >
>
Re: [!!Mass Mail]Re: Move towards binary compatibility to JDK 1.6 or
JDK 1.7 for 1.3.7 RELEASE
Posted by Pierre Smits <pi...@gmail.com>.
FYI: Java 7 is EOL since April 2015
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
On Tue, Dec 8, 2015 at 9:30 AM, Sathwik B P <sa...@gmail.com> wrote:
> I wish to confirm that the migration has worked.
>
> Initial setup:
> ODE war: ODE 1.3.5 with Hibernate 3.2.5
> Tomcat 6.0.44 with Bitronix TM 2.1.4
> JDK 1.5.0_22
> Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
>
>
> Migration setup:
> ODE war: ODE 1.3.7-SNAPSHOT built with minimum binary compatibility to
> JDK 6 with Hibernate 3.3.2
> TomEE 1.7.12
> JDK 1.7.0_80
> Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
>
> We can now move release ODE 1.3.7 with binary compatibility to JDK 6.
>
>
> regards,
> sathwik
>
> On Sun, Dec 6, 2015 at 7:51 PM, Sathwik B P <sa...@gmail.com> wrote:
>
> > Hi,
> >
> > As of now I have faced two issues with the compiling of ODE-1.3.x source
> > after changing the binary compatibility to 1.6
> >
> > A) With the removal of usage of APT tool in Rakefile. How do we generate
> > the Channel and ChannelListener sources. There were 2 options
> > 1) Rewrite the annotation processor using new API
> > 2) Manually add the generated sources to the repo which was generated
> > with JDK 1.5
> >
> > Since we don't use the annotations API in the trunk anymore, I choose to
> > manually add the generated source to the repo.
> >
> >
> > B) XMLBeans, for multiple occurrence element defined in XSD schema
> > generates different methods under JDK 1.5 and JDK 1.6
> >
> > Collection<Something> getSomethingList() -----JDK 1.5
> > Something[] getSomethingArray() ----- JDK 1.6
> >
> > The generated sources from XMLBeans is predominantly used in the
> > Management API within ODE. So, I assume the dependency on this API by
> > external customers would be rare as they would be entitled to use the
> WSDL
> > and XSD.
> >
> > These are the following changes that have resulted due to the changes in
> > the XMLBeans generated sources that has gone into trunk and the same
> needs
> > to be backported to ode 1.3.7 to make it work on JDK 1.6
> >
> >
> https://github.com/apache/ode/commit/ad45177f76a4a7518cb3f79d76e52f55cb86a9c6
> >
> >
> > regards,
> > sathwik
> >
> >
> > On Wed, Dec 2, 2015 at 2:58 PM, Sathwik B P <sa...@gmail.com>
> wrote:
> >
> >> 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 <
> >> Kevin.SEJOURNE@intrinsec.com> 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 <hz...@gmail.com>
> >>> Envoyé : samedi 28 novembre 2015 13:55
> >>> À : user@ode.apache.org
> >>> 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 <sa...@gmail.com>
> >>> 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
> >>> >>
> >>> >
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >
>
Re: [!!Mass Mail]Re: Move towards binary compatibility to JDK 1.6 or
JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
I wish to confirm that the migration has worked.
Initial setup:
ODE war: ODE 1.3.5 with Hibernate 3.2.5
Tomcat 6.0.44 with Bitronix TM 2.1.4
JDK 1.5.0_22
Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
Migration setup:
ODE war: ODE 1.3.7-SNAPSHOT built with minimum binary compatibility to
JDK 6 with Hibernate 3.3.2
TomEE 1.7.12
JDK 1.7.0_80
Mysql: 5.6.27-0ubuntu0.15.04.1 (Ubuntu)
We can now move release ODE 1.3.7 with binary compatibility to JDK 6.
regards,
sathwik
On Sun, Dec 6, 2015 at 7:51 PM, Sathwik B P <sa...@gmail.com> wrote:
> Hi,
>
> As of now I have faced two issues with the compiling of ODE-1.3.x source
> after changing the binary compatibility to 1.6
>
> A) With the removal of usage of APT tool in Rakefile. How do we generate
> the Channel and ChannelListener sources. There were 2 options
> 1) Rewrite the annotation processor using new API
> 2) Manually add the generated sources to the repo which was generated
> with JDK 1.5
>
> Since we don't use the annotations API in the trunk anymore, I choose to
> manually add the generated source to the repo.
>
>
> B) XMLBeans, for multiple occurrence element defined in XSD schema
> generates different methods under JDK 1.5 and JDK 1.6
>
> Collection<Something> getSomethingList() -----JDK 1.5
> Something[] getSomethingArray() ----- JDK 1.6
>
> The generated sources from XMLBeans is predominantly used in the
> Management API within ODE. So, I assume the dependency on this API by
> external customers would be rare as they would be entitled to use the WSDL
> and XSD.
>
> These are the following changes that have resulted due to the changes in
> the XMLBeans generated sources that has gone into trunk and the same needs
> to be backported to ode 1.3.7 to make it work on JDK 1.6
>
> https://github.com/apache/ode/commit/ad45177f76a4a7518cb3f79d76e52f55cb86a9c6
>
>
> regards,
> sathwik
>
>
> On Wed, Dec 2, 2015 at 2:58 PM, Sathwik B P <sa...@gmail.com> wrote:
>
>> 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 <
>> Kevin.SEJOURNE@intrinsec.com> 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 <hz...@gmail.com>
>>> Envoyé : samedi 28 novembre 2015 13:55
>>> À : user@ode.apache.org
>>> 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 <sa...@gmail.com>
>>> 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
>>> >>
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
Re: [!!Mass Mail]Re: Move towards binary compatibility to JDK 1.6 or
JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Hi,
As of now I have faced two issues with the compiling of ODE-1.3.x source
after changing the binary compatibility to 1.6
A) With the removal of usage of APT tool in Rakefile. How do we generate
the Channel and ChannelListener sources. There were 2 options
1) Rewrite the annotation processor using new API
2) Manually add the generated sources to the repo which was generated
with JDK 1.5
Since we don't use the annotations API in the trunk anymore, I choose to
manually add the generated source to the repo.
B) XMLBeans, for multiple occurrence element defined in XSD schema
generates different methods under JDK 1.5 and JDK 1.6
Collection<Something> getSomethingList() -----JDK 1.5
Something[] getSomethingArray() ----- JDK 1.6
The generated sources from XMLBeans is predominantly used in the Management
API within ODE. So, I assume the dependency on this API by external
customers would be rare as they would be entitled to use the WSDL and XSD.
These are the following changes that have resulted due to the changes in
the XMLBeans generated sources that has gone into trunk and the same needs
to be backported to ode 1.3.7 to make it work on JDK 1.6
https://github.com/apache/ode/commit/ad45177f76a4a7518cb3f79d76e52f55cb86a9c6
regards,
sathwik
On Wed, Dec 2, 2015 at 2:58 PM, Sathwik B P <sa...@gmail.com> wrote:
> 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 <
> Kevin.SEJOURNE@intrinsec.com> 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 <hz...@gmail.com>
>> Envoyé : samedi 28 novembre 2015 13:55
>> À : user@ode.apache.org
>> 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 <sa...@gmail.com>
>> 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
>> >>
>> >
>> >
>> >
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: [!!Mass Mail]Re: Move towards binary compatibility to JDK 1.6 or
JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
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 <
Kevin.SEJOURNE@intrinsec.com> 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 <hz...@gmail.com>
> Envoyé : samedi 28 novembre 2015 13:55
> À : user@ode.apache.org
> 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 <sa...@gmail.com>
> 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
> >>
> >
> >
> >
>
>
>
>
>
>
>
>
RE: [!!Mass Mail]Re: Move towards binary compatibility to JDK 1.6 or
JDK 1.7 for 1.3.7 RELEASE
Posted by Kevin SEJOURNE <Ke...@intrinsec.com>.
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 <hz...@gmail.com>
Envoyé : samedi 28 novembre 2015 13:55
À : user@ode.apache.org
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 <sa...@gmail.com> 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
>>
>
>
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7
RELEASE
Posted by Hadrian Zbarcea <hz...@gmail.com>.
+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 <sa...@gmail.com> 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
>>
>
>
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Sathwik B P <sa...@gmail.com>.
Hi pierre,
I am doing good. Thank you.
How's business process discussion going on. If you need us let us know.
Moving to higher jdk has been sitting from long time. The reason i have
brought this issue is because of the use of legacy Annotations Api which
has been removed in jdk 8.
ODE source code current release branch ODE-1.3.x is non compilable on jdk 8.
The new Annotation Api is available in jdk 1.6,1.7
TRUNK branch is compilable on jdk 8 as as we have a completly new Jacob
implementation.
I would prefer jdk 8 as the baselining for 1.3.7 release. Will wait for
responses from the commmunity
On Nov 28, 2015 4:49 AM, "Tammo van Lessen" <tv...@gmail.com> 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 <sa...@gmail.com> 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
> >
>
>
>
> --
> Tammo van Lessen - http://www.taval.de
>
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Tammo van Lessen <tv...@gmail.com>.
+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 <sa...@gmail.com> 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
>
--
Tammo van Lessen - http://www.taval.de
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Tammo van Lessen <tv...@gmail.com>.
+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 <sa...@gmail.com> 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
>
--
Tammo van Lessen - http://www.taval.de
Re: Move towards binary compatibility to JDK 1.6 or JDK 1.7 for 1.3.7 RELEASE
Posted by Pierre Smits <pi...@gmail.com>.
Hi Sathwik,
How's life?
I guess, the majority starts out with ODE baselining against jdk 1.5. But
as this is way out of the reliability range, any *new* version of ODE can
be set to use a newer version. I suggest to skip the 1.6 variant of Java as
this is already EOL-ed by the owner and shoot for 1.7. You might even
consider opting for 1.8, but if you do, be sure to communicate this
frequently through various channels.
If you decide not to opt for 1.8 now, just put it on the roadmap of ODE.
Adopters can plan better, when they know what lies ahead.
Best regards,
Pierre Smits
*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/
On Fri, Nov 27, 2015 at 7:57 AM, Sathwik B P <sa...@gmail.com> 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
>