|
46 | 46 | * <p> An attach provider implementation is typically tied to a Java virtual |
47 | 47 | * machine implementation, version, or even mode of operation. That is, a specific |
48 | 48 | * provider implementation will typically only be capable of attaching to |
49 | | - * a specific Java virtual machine implementation or version. For example, Sun's |
| 49 | + * a specific Java virtual machine implementation or version. For example, Oracle's |
50 | 50 | * JDK implementation ships with provider implementations that can only attach to |
51 | | - * Sun's <i>HotSpot</i> virtual machine. In general, if an environment |
| 51 | + * Oracle's <i>HotSpot</i> virtual machine. In general, if an environment |
52 | 52 | * consists of Java virtual machines of different versions and from different |
53 | 53 | * vendors then there will be an attach provider implementation for each |
54 | 54 | * <i>family</i> of implementations or versions. |
55 | 55 | * |
56 | 56 | * <p> An attach provider is identified by its {@link #name <i>name</i>} and |
57 | 57 | * {@link #type <i>type</i>}. The <i>name</i> is typically, but not required to |
58 | | - * be, a name that corresponds to the VM vendor. The Sun JDK implementation, |
59 | | - * for example, ships with attach providers that use the name <i>"sun"</i>. The |
| 58 | + * be, a name that corresponds to the VM vendor. The Oracle JDK implementation, |
| 59 | + * for example, ships with attach providers that use the package name <i>"sun"</i> |
| 60 | + * (for historical reasons). The |
60 | 61 | * <i>type</i> typically corresponds to the attach mechanism. For example, an |
61 | 62 | * implementation that uses the Doors inter-process communication mechanism |
62 | 63 | * might use the type <i>"doors"</i>. The purpose of the name and type is to |
|
0 commit comments