directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob Barrett" <>
Subject RE: [ApacheDS] Moving to JDK 5.0
Date Fri, 23 Sep 2005 16:57:03 GMT
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 [] 
	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.
	2005/9/24, Jacob Barrett <>: 

		Not in with my compiler from Sun.
-source 1.5 -target 1.4 src/java5/
		javac: source release 1.5 requires target release 1.5
-source 1.4 -target 1.4 src/java5/
		src/java5/ generics are not supported in
-source 1.4
		(try -source 1.5 to enable generics)
		public class Test<T>
		1 error


			From: Marc Boorshtein
<> ] 
			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).
			On 9/23/05, Jacob Barrett
> 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

View raw message