comparison graal/com.oracle.jvmci.service/src/com/oracle/jvmci/service/Service.java @ 21760:55058b8000ea

updated javadoc to document that JVMCI services are disjoint from the standard service loading mechanism and tightened generic type constraint such that Services and @ServiceProcessor can only be used with classes implementing Service
author Doug Simon <doug.simon@oracle.com>
date Sat, 06 Jun 2015 09:23:37 +0200
parents 93f282187d90
children
comparison
equal deleted inserted replaced
21759:75daca0c6a0f 21760:55058b8000ea
20 * or visit www.oracle.com if you need additional information or have any 20 * or visit www.oracle.com if you need additional information or have any
21 * questions. 21 * questions.
22 */ 22 */
23 package com.oracle.jvmci.service; 23 package com.oracle.jvmci.service;
24 24
25 import java.util.*;
26
25 /** 27 /**
26 * Denotes a service that may be efficiently loaded by {@link Services#load(Class)}. 28 * Denotes a JVMCI service that can be loaded by {@link Services#load(Class)} or
29 * {@link Services#loadSingle(Class, boolean)}. JVMCI services differ from
30 * {@linkplain ServiceLoader#load(Class) standard} services in that they may have implementations
31 * hidden behind a class loader not accessible to applications. For this reason,
32 * {@link Services#load(Class)} and {@link Services#loadSingle(Class, boolean)} perform
33 * {@link SecurityManager} checks.
34 *
35 * @see Services
36 * @see ServiceProvider
27 */ 37 */
28 public interface Service { 38 public interface Service {
29 } 39 }