SUN just retired JDK 1.4.  Shall we go 1.5 in the 1.1 branch?  1.0 can
be for jdk 1.4 use.

Alex

[ Post a follow-up to this message ]

[ Post a follow-up to this message ]

Not that it neccessarily concerns you guys, but the biggest problem we
have re JDK version upgrades is IBM's websphere appserver which always
seems to lag far behind due to having its own IBM-authored JVM.

Our customers aren't keen to upgrade until websphere has, which ties our ha=
nds.

I gather that pretty much all new work will be going into AD 1.1 after
a month or so, correct?

[ Post a follow-up to this message ]

Norbet Reilly wrote:
> Not that it neccessarily concerns you guys, but the biggest problem we
> have re JDK version upgrades is IBM's websphere appserver which always
> seems to lag far behind due to having its own IBM-authored JVM.
>
> Our customers aren't keen to upgrade until websphere has, which ties our h
ands.
>
> I gather that pretty much all new work will be going into AD 1.1 after
> a month or so, correct?
>
I think so norbet.  All new features will go into 1.1.  1.0 is a feature
frozen branch where we only fix bugs as they are reported.

Alex

[ Post a follow-up to this message ]

As I suspected ... but ouch ;-)

Can I ask where you heard about JDK1.4 being dropped? The Sun J2SE
download area doesn't include it anymore, but I get the feeling that
is just as a bug as J2EE 1.2 is still downloadable and not
end-of-lifed yet...

[ Post a follow-up to this message ]

Norbet Reilly wrote:
> As I suspected ... but ouch ;-)
>
> Can I ask where you heard about JDK1.4 being dropped? The Sun J2SE
> download area doesn't include it anymore, but I get the feeling that
> is just as a bug as J2EE 1.2 is still downloadable and not
> end-of-lifed yet...
>
This is exactly what I noticed.  Sun seems to be kicking us to move from
1.4 this way.

Alex

[ Post a follow-up to this message ]

On 3/7/06, Alex Karasulu <aok123-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org> wrote:
>
> SUN just retired JDK 1.4.  Shall we go 1.5 in the 1.1 branch?  1.0 can
> be for jdk 1.4 use.


Another big +1 here. 

Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

[ Post a follow-up to this message ]

Norbet Reilly a écrit :

>Not that it neccessarily concerns you guys, but the biggest problem we
>have re JDK version upgrades is IBM's websphere appserver which always
>seems to lag far behind due to having its own IBM-authored JVM.
>
>Our customers aren't keen to upgrade until websphere has, which ties our ha
nds.
>
>I gather that pretty much all new work will be going into AD 1.1 after
>a month or so, correct?
>
>
>
Hi Norbert,

your concern is right, as far as IBM consider that WebSphere 5.x is
still a live product. By the end of this year, WebSphere 5.x will be
dead and all IBM users will be ask to switch to WebSphere 6.x, if they
want to be supported.

I know that customer with working applications may perfectly continue to
run them on non maintained versions of WS, but we still have a 1.0
version which will be perfect for that. btw, WebSphere 4.0 is using a
1.3 version JDK, and we still have people around the world using WS4
(trust me : I'm a living witness 

So having a 1.0/jdk 1.4 version and a 1.1/jdk5 version just seems
reasonnable to me.

I'm just thinking about Geronimo which needs a 1.4 JDK compatible source
base. What should we do? Do we have to "inject" all the new features we
will pour into 1.1 back to 1.0 ? That's the good question in my mind. I
don't know if we should tighten ADS developper (I'm thinking of Mina)
into a JDK version that does not fit their needs, and I don't know if we
should do it the Tomcat way (having a 5.0/JDK1.4 and a 5.5/JDK5
versions), which will generate more work for all of us.

Further more, the longer we will wait for this move, the more we will be
stuck with the user base on old JVM...

I'll vote +1, strongly.

[ Post a follow-up to this message ]

Alex Karasulu wrote:
> SUN just retired JDK 1.4.  Shall we go 1.5 in the 1.1 branch?  1.0 can
> be for jdk 1.4 use.
>
> Alex
Although 1.5 will make life really easier we should think about it
carefully. 1.1 will probably be released in 4-5 months and so in this
case we assume that the users will adopt 1.5 by this mid-summer. (Will
they be ready?) It will make things easier for developers but the more
important is users. But I still favor 1.5 from a technical point of view.

--
Ersin

[ Post a follow-up to this message ]

Thanks for the update on IBM's plans.

Are you certain that WAS 6 is delivered with JDK1.5, that wasn't my
expectation and a quick google showed up some people using WAS 6 and
JDK1.4. Looking at
http://www-306.ibm.com/software/web...v/was/features/ it
seems it supports J2EE 1.4 (which Sun says needs JDK 1.5) but only JDK
1.4, so presumably they're using some additional back-ported JDK1.5
libraries but only the JDK1.4 JVM.

Anyway, I know websphere support isn't most probably a pivotal issue
for the AD development community, but I just trying to point out that
mandating JDK1.5 at this point may cut you off from some otherwise
keen customers - like me ;-)

[ Post a follow-up to this message ]