In an audit done after a DSR upgrade from s9u6, cluster All plus OEM, to s10u1 b4 pkgchk found the following errors:

ERROR: /usr/bin/javaws
    pathname not symbolically linked to <../j2se/jre/javaws/javaws>
ERROR: /usr/java
    pathname not symbolically linked to <./j2se>
Sun Microsystems Inc. SunOS 5.9 Generic May 2002
# /usr/j2se/bin/java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
# /usr/bin/java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
# cat /etc/release
                        Solaris 9 4/04 s9s_u6wos_08a SPARC
           Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.
                        Use is subject to license terms.
                             Assembled 22 March 2004
#

----------------------------

Sun Microsystems Inc. SunOS 5.10 Generic January 2005
# /usr/j2se/bin/java -version
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b02)
Java HotSpot(TM) Client VM (build 1.4.2_08-b02, mixed mode)
# /usr/bin/java -version
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
# cat /etc/release
                       Solaris 10 10/05 s10s_u1wos_14 SPARC
           Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 07 September 2005
#
# pkgchk -n SUNWj3rt
ERROR: /usr/bin/javaws
    pathname not symbolically linked to <../j2se/jre/javaws/javaws>
ERROR: /usr/java
    pathname not symbolically linked to <./j2se>
I just got done installing Solaris 9 Operating Environment 4/04 from FCS DVD.
I got the following information:
# /usr/j2se/bin/java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
# /usr/bin/java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
# cat /etc/release
                        Solaris 9 4/04 s9s_u6wos_08a SPARC
           Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.
                        Use is subject to license terms.
                             Assembled 22 March 2004

from this I assume the bug shouldn't have been closed for the reason given.
The problem reproduces if we upgrade jdk from 1.4.2_04 upgrade to 1.4.2_05+
Jdk 1.5 or 6.0 have no such problem, so it should be assigned to jdk sustaining team.