|
Home > Archive > Apache Directory Project > September 2005 > [ApacheDS] Moving to JDK 5.0
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[ApacheDS] Moving to JDK 5.0
|
|
| Alex Karasulu 2005-09-23, 2:45 am |
| Hi all,
We intend in the next release to move to jdk 5.0 without backward
compatability with JDK 1.4. This was a hard decision to make but some
features in jdk 5.0 are required for us to make ApacheDS LDAPv3 compatable.
Namely we are going to be using jdk 5.0 features for SASL support.
We have drawn up a roadmap to reach a 1.0 release for ApacheDS by March
of 2006. By that time we suspect the jdk 5.0 to be the standard JDK in
production. Here's the roadmap btw:
http://docs.safehaus.org/pages/view...ion?pageId=2394
We will move this roadmap into the ASF JIRA as soon as we distill fine
grained tasks from it. Please excuse the storm of JIRA issue movements
that will follow.
All those that want to use ApacheDS with 1.4 should use releases 0.9.2
and below. 0.9.3 is debatable but 0.9.4 will definately use 5.0
features and hence will be 1.4 incompatable.
Thanks,
Alex
| |
| Enrique Rodriguez 2005-09-23, 2:45 am |
| Alex Karasulu wrote:
> Hi all,
>
> We intend in the next release to move to jdk 5.0 without backward
> compatability with JDK 1.4. This was a hard decision to make but some
> features in jdk 5.0 are required for us to make ApacheDS LDAPv3 compatable.
>
> Namely we are going to be using jdk 5.0 features for SASL support.
> We have drawn up a roadmap to reach a 1.0 release for ApacheDS by March
> of 2006. By that time we suspect the jdk 5.0 to be the standard JDK in
> production. Here's the roadmap btw:
>
> http://docs.safehaus.org/pages/view...ion?pageId=2394
I've been looking forward to this for a while now. 1.5 has been out for
over a year and given how much more time we need to complete the
roadmap, let alone any sort of enterprise adoption, it makes perfect
sense to take advantage of many of the features in 1.5. In addition to
SASL, we already require 1.5 for SSL in MINA and I, for one, would like
to use some of the new concurrent collections and crypto.
Enrique
| |
| Brett Porter 2005-09-23, 2:45 am |
| +1 for the server. Please consider differently for other consumable
libraries (eg -naming probably should remain 1.3/1.4, I'm not sure
about things like MINA).
Before jumping in, I know this was discussed maybe 6 months ago -
someone might like to dig in the archives and see if there were any
cases against it that still hold.
- Brett
On 9/23/05, Alex Karasulu <aok123-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org> wrote:
> Hi all,
>
> We intend in the next release to move to jdk 5.0 without backward
> compatability with JDK 1.4. This was a hard decision to make but some
> features in jdk 5.0 are required for us to make ApacheDS LDAPv3 compatabl=
e.
>
> Namely we are going to be using jdk 5.0 features for SASL support.
>
> We have drawn up a roadmap to reach a 1.0 release for ApacheDS by March
> of 2006. By that time we suspect the jdk 5.0 to be the standard JDK in
> production. Here's the roadmap btw:
>
> http://docs.safehaus.org/pages/view...n?pageId=3D2394
>
> We will move this roadmap into the ASF JIRA as soon as we distill fine
> grained tasks from it. Please excuse the storm of JIRA issue movements
> that will follow.
>
> All those that want to use ApacheDS with 1.4 should use releases 0.9.2
> and below. 0.9.3 is debatable but 0.9.4 will definately use 5.0
> features and hence will be 1.4 incompatable.
>
> Thanks,
> Alex
>
>
| |
| Nick Faiz 2005-09-23, 2:45 am |
| Hi Alex,
I remember this being discussed earlier on and can definitely see how
useful the move to 1.5 will be.
Thanks for the roadmap - it looks really good.
Cheers,
Nick
Alex Karasulu wrote:
> Hi all,
>
> We intend in the next release to move to jdk 5.0 without backward
> compatability with JDK 1.4. This was a hard decision to make but some
> features in jdk 5.0 are required for us to make ApacheDS LDAPv3 compatable.
>
> Namely we are going to be using jdk 5.0 features for SASL support.
> We have drawn up a roadmap to reach a 1.0 release for ApacheDS by March
> of 2006. By that time we suspect the jdk 5.0 to be the standard JDK in
> production. Here's the roadmap btw:
>
> http://docs.safehaus.org/pages/view...ion?pageId=2394
>
> We will move this roadmap into the ASF JIRA as soon as we distill fine
> grained tasks from it. Please excuse the storm of JIRA issue movements
> that will follow.
>
> All those that want to use ApacheDS with 1.4 should use releases 0.9.2
> and below. 0.9.3 is debatable but 0.9.4 will definately use 5.0
> features and hence will be 1.4 incompatable.
>
> Thanks,
> Alex
>
--
ATLASSIAN - http://www.atlassian.com/
Confluence - the enterprise wiki - tried it yet?
http://www.atlassian.com/confluence/
--
| |
| Trustin Lee 2005-09-23, 2:45 am |
| I agree with what Brett says here. 
Trustin
2005/9/23, Brett Porter <brett.porter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>
> +1 for the server. Please consider differently for other consumable
> libraries (eg -naming probably should remain 1.3/1.4, I'm not sure
> about things like MINA).
>
> Before jumping in, I know this was discussed maybe 6 months ago -
> someone might like to dig in the archives and see if there were any
> cases against it that still hold.
>
> - Brett
>
> On 9/23/05, Alex Karasulu <aok123-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org> wrote:
> compatable.
>
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Alex Karasulu 2005-09-23, 2:45 am |
| Trustin Lee wrote:
> I agree with what Brett says here.
>
> Trustin
>
> 2005/9/23, Brett Porter <brett.porter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> <mailto:brett.porter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>>:
>
> +1 for the server. Please consider differently for other consumable
> libraries (eg -naming probably should remain 1.3/1.4, I'm not sure
> about things like MINA).
>
Oh yes to be more exact this is for ApacheDS and not other libraries
like naming of course.
Alex
| |
| Emmanuel Lecharny 2005-09-23, 2:45 am |
| +1 for JDK 5.0, for the server only as Brett suggested.
On Fri, 2005-09-23 at 00:20 -0400, Alex Karasulu wrote:
> Hi all,
>
> We intend in the next release to move to jdk 5.0 without backward
> compatability with JDK 1.4. This was a hard decision to make but some
> features in jdk 5.0 are required for us to make ApacheDS LDAPv3 compatable.
>
> Namely we are going to be using jdk 5.0 features for SASL support.
>
> We have drawn up a roadmap to reach a 1.0 release for ApacheDS by March
> of 2006. By that time we suspect the jdk 5.0 to be the standard JDK in
> production. Here's the roadmap btw:
>
> http://docs.safehaus.org/pages/view...ion?pageId=2394
>
> We will move this roadmap into the ASF JIRA as soon as we distill fine
> grained tasks from it. Please excuse the storm of JIRA issue movements
> that will follow.
>
> All those that want to use ApacheDS with 1.4 should use releases 0.9.2
> and below. 0.9.3 is debatable but 0.9.4 will definately use 5.0
> features and hence will be 1.4 incompatable.
>
> Thanks,
> Alex
>
> ---------------------------------------------------------------------------------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>
| |
| Julien Vermillard 2005-09-23, 7:45 am |
| Perhaps you don't know retroweeaver. In resume : Compile on JDK1.5, Run
on JDK1.4.
http://retroweaver.sourceforge.net/
Perhaps that could help you to deploy 1.5 code on 1.4 JVM
Julien
| |
| Brett Porter 2005-09-23, 7:45 am |
| I believe that is for JDK 5.0 language features - however the guys are
looking for JDK runtime features that are not available in jdk 1.4's
rt.jar.
- Brett
On 9/23/05, Julien Vermillard <jvermillard-hxtJVsqPMRdGWvitb5QawA@public.gmane.org> wrote:
> Perhaps you don't know retroweeaver. In resume : Compile on JDK1.5, Run
> on JDK1.4.
>
> http://retroweaver.sourceforge.net/
>
> Perhaps that could help you to deploy 1.5 code on 1.4 JVM
>
> Julien
>
>
| |
| Marc Boorshtein 2005-09-23, 7:45 am |
| I've been on JDK 1.5 for a couple of months now and the generics support
alone is worth it (but thats backwards compatible). Besides, I would think
that as a stand alone server the JRE wouldn't be an issue as it's pretty
common practic to distribute a JRE with Java server applications.
Marc
On 9/23/05, Brett Porter <brett.porter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I believe that is for JDK 5.0 language features - however the guys are
> looking for JDK runtime features that are not available in jdk 1.4's
> rt.jar.
>
> - Brett
>
> On 9/23/05, Julien Vermillard <jvermillard-hxtJVsqPMRdGWvitb5QawA@public.gmane.org> wrote:
>
| |
| Jacob Barrett 2005-09-23, 5:45 pm |
| While I agree that a move to 1.5 would be nice you have to consider that
not all platforms support 1.5 at the moment. In particular IBM z/OS
which is a typical platform that my company tends to deploy into.
FreeBSD is only in the beta phase of producing a native 1.5, you can run
the Linux version in emulation. Also, most of the application servers
out there are still only 1.4, so limiting to 1.5 only works in a
"standalone" mode.
=20
If there is a way to take advantage of the language constructs in 1.5
but target 1.4 byte code then I would be all for it. Retroweaver is
interesting, but does it produce production stable byte code?
Has anyone on here REALLY used it in a production environment?
| |
| Trustin Lee 2005-09-23, 5:45 pm |
| Hi,
2005/9/24, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org>:
>
> If there is a way to take advantage of the language constructs in 1.5
> but target 1.4 byte code then I would be all for it. Retroweaver is
> interesting, but does it produce production stable byte code?
>
> Has anyone on here REALLY used it in a production environment?
>
It seems like the author and some users are using Retroweaver in production
environment. But the author is not releasing a new version even if there has
been several bug reports and patches.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Marc Boorshtein 2005-09-23, 5:45 pm |
| Or at least i thought the language features were backwords compatible....
Marc
On 9/23/05, Marc Boorshtein <mboorshtein-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Well, the language features are backwards compatible (generics & enums). I
> think the main problem is the class libraries. Prior to 1.4 new labraries
> went first into the "javax" package first, so you could use them in older
> JREs.
>
> As to anyone using it in production, I'd be very doubtfull that any
> commercial apps are shipping 1.5 (I know several that still require 1.3).
>
> Marc
>
> On 9/23/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
>
>
| |
| Marc Boorshtein 2005-09-23, 5:45 pm |
| Well, the language features are backwards compatible (generics & enums). I
think the main problem is the class libraries. Prior to 1.4 new labraries
went first into the "javax" package first, so you could use them in older
JREs.
As to anyone using it in production, I'd be very doubtfull that any
commercial apps are shipping 1.5 (I know several that still require 1.3).
Marc
On 9/23/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
>
> While I agree that a move to 1.5 would be nice you have to consider that
> not all platforms support 1.5 at the moment. In particular IBM z/OS
> which is a typical platform that my company tends to deploy into.
> FreeBSD is only in the beta phase of producing a native 1.5, you can run
> the Linux version in emulation. Also, most of the application servers
> out there are still only 1.4, so limiting to 1.5 only works in a
> "standalone" mode.
>
> If there is a way to take advantage of the language constructs in 1.5
> but target 1.4 byte code then I would be all for it. Retroweaver is
> interesting, but does it produce production stable byte code?
>
> Has anyone on here REALLY used it in a production environment?
>
| |
| Jacob Barrett 2005-09-23, 5:45 pm |
| > From: Alex Karasulu [mailto:aok123-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org]=20
> We intend in the next release to move to jdk 5.0 without=20
> backward compatability with JDK 1.4. This was a hard=20
> decision to make but some features in jdk 5.0 are required=20
> for us to make ApacheDS LDAPv3 compatable.
>=20
> Namely we are going to be using jdk 5.0 features for SASL support.=20
I assume there are many more factors in this decision, but have you
considered using the original JSR implementation which is 1.4
compatible? The packages, class names and JavaDocs are from what I can
tell identical.
http://www.worldspot.com/jsr28/
Sorry if I am beating dead horse here. I just know 1.5 is way out of
the question where I work so I am not looking forward to forking away
from the main trunk of the ApacheDS. Call me selfish...
| |
| Jacob Barrett 2005-09-23, 5:45 pm |
| Not in with my compiler from Sun.
C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac -source 1.5
-target 1.4 src/java5/Test.java
javac: source release 1.5 requires target release 1.5
C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac -source 1.4
-target 1.4 src/java5/Test.java
src/java5/Test.java:10: generics are not supported in -source 1.4
(try -source 1.5 to enable generics)
public class Test<T>
^
1 error
________________________________
From: Marc Boorshtein [mailto:mboorshtein-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: Friday, September 23, 2005 8:45 AM
To: Apache Directory Developers List
Subject: Re: [ApacheDS] Moving to JDK 5.0
Well, the language features are backwards compatible (generics &
enums). I think the main problem is the class libraries. Prior to 1.4
new labraries went first into the "javax" package first, so you could
use them in older JREs.
As to anyone using it in production, I'd be very doubtfull that
any commercial apps are shipping 1.5 (I know several that still require
1.3).
Marc
On 9/23/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
While I agree that a move to 1.5 would be nice you have
to consider that
not all platforms support 1.5 at the moment. In
particular IBM z/OS
which is a typical platform that my company tends to
deploy into.
FreeBSD is only in the beta phase of producing a native
1.5, you can run
the Linux version in emulation. Also, most of the
application servers
out there are still only 1.4, so limiting to 1.5 only
works in a
"standalone" mode.
If there is a way to take advantage of the language
constructs in 1.5
but target 1.4 byte code then I would be all for it.
Retroweaver is
interesting, but does it produce production stable byte
code?
Has anyone on here REALLY used it in a production
environment?
| |
| Marc Boorshtein 2005-09-23, 5:45 pm |
| Yeah, i thought it was OK to run on 1.4 once compiled, but I can't remember
where I read that from.
Marc
On 9/23/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
>
> Not in with my compiler from Sun.
> C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac -source 1.5-target
> 1.4 src/java5/Test.java
> javac: source release 1.5 requires target release 1.5
> C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac -source 1.4-target
> 1.4 src/java5/Test.java
> src/java5/Test.java:10: generics are not supported in -source 1.4
> (try -source 1.5 to enable generics)
> public class Test<T>
> ^
> 1 error
>
> ------------------------------
> *From:* Marc Boorshtein [mailto:mboorshtein-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
> *Sent:* Friday, September 23, 2005 8:45 AM
> *To:* Apache Directory Developers List
> *Subject:* Re: [ApacheDS] Moving to JDK 5.0
>
> Well, the language features are backwards compatible (generics & enums). I
> think the main problem is the class libraries. Prior to 1.4 new labraries
> went first into the "javax" package first, so you could use them in older
> JREs.
>
> As to anyone using it in production, I'd be very doubtfull that any
> commercial apps are shipping 1.5 (I know several that still require 1.3).
>
> Marc
>
> On 9/23/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
>
>
| |
| Trustin Lee 2005-09-23, 5:45 pm |
| What retroweaver do is manipulation of Java 1.5 bytecodes to transform your
1.5 classes (version 0.49) into 1.4 classes (version 0.48). And it replaces
names of "java.*" classes introduced first in Java 5 with
backward-compatible ones in retroweaver.jar. It's quite tricky, but it
works. I even saw a guy who's substituting java.util.concurrent with the
backport library though it is not included in official retroweaver
distribution.
Trustin
2005/9/24, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org>:
>
> Not in with my compiler from Sun.
> C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac -source 1.5-target
> 1.4 src/java5/Test.java
> javac: source release 1.5 requires target release 1.5
> C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac -source 1.4-target
> 1.4 src/java5/Test.java
> src/java5/Test.java:10: generics are not supported in -source 1.4
> (try -source 1.5 to enable generics)
> public class Test<T>
> ^
> 1 error
>
> ------------------------------
> *From:* Marc Boorshtein [mailto:mboorshtein-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org<https://mail.google..com/mail?view=...ublic.gmane.org>]
>
> *Sent:* Friday, September 23, 2005 8:45 AM
> *To:* Apache Directory Developers List
> *Subject:* Re: [ApacheDS] Moving to JDK 5.0
>
> Well, the language features are backwards compatible (generics & enums). I
> think the main problem is the class libraries. Prior to 1.4 new labraries
> went first into the "javax" package first, so you could use them in older
> JREs.
>
> As to anyone using it in production, I'd be very doubtfull that any
> commercial apps are shipping 1.5 (I know several that still require 1.3).
>
> Marc
>
> On 9/23/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org<https://mail.google.com/mail?view=c...ublic.gmane.org>>
> wrote:
>
>
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Jacob Barrett 2005-09-23, 5:45 pm |
| C:\devel\workspace\java5>c:\java\j2sdk1.4.2_07\bin\java -cp bin
java5.Test
Exception in thread "main" java.lang.UnsupportedClassVersionError:
java5/Test (Unsupported major.minor version 49.0)
________________________________
From: Marc Boorshtein [mailto:mboorshtein-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: Friday, September 23, 2005 9:15 AM
To: Apache Directory Developers List
Subject: Re: [ApacheDS] Moving to JDK 5.0
Yeah, i thought it was OK to run on 1.4 once compiled, but I
can't remember where I read that from.
Marc
On 9/23/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
Not in with my compiler from Sun.
C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac
-source 1.5 -target 1.4 src/java5/Test.java
javac: source release 1.5 requires target release 1.5
C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac
-source 1.4 -target 1.4 src/java5/Test.java
src/java5/Test.java:10: generics are not supported in
-source 1.4
(try -source 1.5 to enable generics)
public class Test<T>
^
1 error
________________________________
From: Marc Boorshtein
[mailto:mboorshtein-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: Friday, September 23, 2005 8:45 AM
To: Apache Directory Developers List
Subject: Re: [ApacheDS] Moving to JDK 5.0
Well, the language features are backwards
compatible (generics & enums). I think the main problem is the class
libraries. Prior to 1.4 new labraries went first into the "javax"
package first, so you could use them in older JREs.
As to anyone using it in production, I'd be very
doubtfull that any commercial apps are shipping 1.5 (I know several that
still require 1.3).
Marc
On 9/23/05, Jacob Barrett
<JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
While I agree that a move to 1.5 would
be nice you have to consider that
not all platforms support 1.5 at the
moment. In particular IBM z/OS
which is a typical platform that my
company tends to deploy into.
FreeBSD is only in the beta phase of
producing a native 1.5, you can run
the Linux version in emulation. Also,
most of the application servers
out there are still only 1.4, so
limiting to 1.5 only works in a
"standalone" mode.
If there is a way to take advantage of
the language constructs in 1.5
but target 1.4 byte code then I would be
all for it. Retroweaver is
interesting, but does it produce
production stable byte code?
Has anyone on here REALLY used it in a
production environment?
| |
| Jacob Barrett 2005-09-23, 5:45 pm |
| Sounds promising, but I don't like your comments about the author not
releasing new versions. Messing with the byte code makes me nervous for
debugging customer found issues.
For the java.util.concurrent deal I wrote a library that has all the
same classes that wrap factories that load either the 1.5 or the
backport impls. We use it internally now for concurrency stuff since we
have to support Java 1.4. Heck we just stopped supporting 1.3 with this
upcoming release and I have a sneaking suspicion that we will be asked
to support it about 3 days before we release.
I think I will have to download and check out this retroweaver deal.
________________________________
From: Trustin Lee [mailto:trustin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
Sent: Friday, September 23, 2005 9:17 AM
To: Apache Directory Developers List
Subject: Re: [ApacheDS] Moving to JDK 5.0
What retroweaver do is manipulation of Java 1.5 bytecodes to
transform your 1.5 classes (version 0.49) into 1.4 classes (version
0.48). And it replaces names of "java.*" classes introduced first in
Java 5 with backward-compatible ones in retroweaver.jar. It's quite
tricky, but it works. I even saw a guy who's substituting
java.util.concurrent with the backport library though it is not included
in official retroweaver distribution.
Trustin
2005/9/24, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org>:
Not in with my compiler from Sun.
C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac
-source 1.5 -target 1.4 src/java5/Test.java
javac: source release 1.5 requires target release 1.5
C:\devel\workspace\java5>c:\java\jdk1.5.0_01\bin\javac
-source 1.4 -target 1.4 src/java5/Test.java
src/java5/Test.java:10: generics are not supported in
-source 1.4
(try -source 1.5 to enable generics)
public class Test<T>
^
1 error
________________________________
From: Marc Boorshtein
[mailto:mboorshtein-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
<https://mail.google.com/mail?view=c...ublic.gmane.org> ]
Sent: Friday, September 23, 2005 8:45 AM
To: Apache Directory Developers List
Subject: Re: [ApacheDS] Moving to JDK 5.0
Well, the language features are backwards
compatible (generics & enums). I think the main problem is the class
libraries. Prior to 1.4 new labraries went first into the "javax"
package first, so you could use them in older JREs.
As to anyone using it in production, I'd be very
doubtfull that any commercial apps are shipping 1.5 (I know several that
still require 1.3).
Marc
On 9/23/05, Jacob Barrett
<JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org
<https://mail.google.com/mail?view=c...achmatewrq..com>
> wrote:
While I agree that a move to 1.5 would
be nice you have to consider that
not all platforms support 1.5 at the
moment. In particular IBM z/OS
which is a typical platform that my
company tends to deploy into.
FreeBSD is only in the beta phase of
producing a native 1.5, you can run
the Linux version in emulation. Also,
most of the application servers
out there are still only 1.4, so
limiting to 1.5 only works in a
"standalone" mode.
If there is a way to take advantage of
the language constructs in 1.5
but target 1.4 byte code then I would be
all for it. Retroweaver is
interesting, but does it produce
production stable byte code?
Has anyone on here REALLY used it in a
production environment?
--
what we call human nature is actually human habit
--
http://gleamynode.net/
| |
| Brett Porter 2005-09-23, 5:45 pm |
| This sounds worth investigating.
Another thing to consider might be what impact this will have on
Geronimo's directory integration - I assume they are supporting 1.4.
I know March is still some time away, but these things do tend to move
slowly - I usually take a "last 2 versions" approach
I'm still +1, after having exhausted other options such as below
(includes reviewing previous reasons as I mentioned earlier).
Cheers,
Brett
On 9/24/05, Jacob Barrett <JacobBa-fpjMuKYJhitg9JdGY8MUfAC/G2K4zDHf@public.gmane.org> wrote:
> I assume there are many more factors in this decision, but have you
> considered using the original JSR implementation which is 1.4
> compatible? The packages, class names and JavaDocs are from what I can
> tell identical.
>
> http://www.worldspot.com/jsr28/
| |
| Alex Karasulu 2005-09-24, 2:45 am |
| Brett Porter wrote:
>This sounds worth investigating.
>
>Another thing to consider might be what impact this will have on
>Geronimo's directory integration - I assume they are supporting 1.4.
>
>
>
Yeah just checked with them about this on the Geronimo list. I think we
better find a way to stick to JDK 1.4 at least with respect to the core
which is the primary part that is embedded.
Basically for SASL we need (hopefully) to only change a single class,
BindHandler, which is actually pluggable. If Jacob's suggestion can be
used then we're good to go and our only concern is SSL. However with
with SASL our IESG security requirements are met and we can say the
server is LDAPv3 compative while on JDK 1.4.
So what does this mean WRT a move to JDK 1.4. Well let me just say this
.... everybody I know and their grandmother contacted me or someone on
this team about the potential move to 5.0. It's making lots of people
freak out. We really need to think about every possible means to stay
compatible with 1.4.
Alex
| |
| Noel J. Bergman 2005-09-24, 5:45 pm |
| If we want to be embedded in J2EE applications, we cannot practically
require anything more than J2SE 1.4. If ApacheDS were to require JDK 1.5 it
will effectively preclude many of us from using it in embedded situations.
--- Noel
| |
| Emmanuel Lecharny 2005-09-24, 5:45 pm |
| Well, that's very valid points.
What about focusing on 1.4 for the 1.0 version, as all the code is
already 1.4 compliant, dealing with this SASL 1.5 issue by backporting
the offending class (something very commonly done in old days when
dealing with 1.1.8 -> 1.2 or 1.2 -> 1.3 Java porting), and planning to
use 1.5 for ApacheDS 2.0?
Then we will be able to carry two different versions. The ADS 1.0 will
then be a dead branch, with fixes only.
Wdyt ?
Emmanuel.
On Sat, 2005-09-24 at 10:15 -0400, Noel J. Bergman wrote:
> If we want to be embedded in J2EE applications, we cannot practically
> require anything more than J2SE 1.4. If ApacheDS were to require JDK 1.5 it
> will effectively preclude many of us from using it in embedded situations.
>
> --- Noel
>
> ---------------------------------------------------------------------------------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>
|
|
|
|
|