-
Enhancement
-
Resolution: Fixed
-
P3
-
5.0
-
b08
-
generic
-
solaris_10
-
Not verified
Problem:
The problem is two fold:
1) There has been a low level of background requests to be able
to easily execute the most advanced JVM on the system. Entities
with this desire are our greatest friends because the believe
in our ability to be backward compatable (or they just never
thought about it). However, mostly this seems to be a desire
to have equivalent behavior between Solaris and Windows.
2) Internal utilization of the the Multiple JRE mechanism has been
slowed because a well known name to an initial mJRE enabled
java launcher isn't available.
Note that although JES hasn't directly requested this, this offers
a solution to one of their installation difficulties. JDS will
probably run into the same difficulty (they've just restricted
their release compatibility matrix so much at the moment, that
they haven't realized the problem yet).
The problem is two fold:
1) There has been a low level of background requests to be able
to easily execute the most advanced JVM on the system. Entities
with this desire are our greatest friends because the believe
in our ability to be backward compatable (or they just never
thought about it). However, mostly this seems to be a desire
to have equivalent behavior between Solaris and Windows.
2) Internal utilization of the the Multiple JRE mechanism has been
slowed because a well known name to an initial mJRE enabled
java launcher isn't available.
Note that although JES hasn't directly requested this, this offers
a solution to one of their installation difficulties. JDS will
probably run into the same difficulty (they've just restricted
their release compatibility matrix so much at the moment, that
they haven't realized the problem yet).