xapi.reflect.X_Reflect Maven / Gradle / Ivy

Show more of this group Show more artifacts with this name
Show all versions of xapi-dev Show documentation

Everything needed to run a comprehensive dev environment. Just type X_ and pick a service from autocomplete; new dev modules will be added as they are built. The only dev service not included in the uber jar is xapi-dev-maven, as it includes all runtime dependencies of maven, adding ~4 seconds to build time, and 6 megabytes to the final output jar size (without xapi-dev-maven, it's ~1MB).

The newest version!

package xapi.reflect;

import javax.inject.Provider;

import xapi.inject.X_Inject;
import xapi.reflect.service.ReflectionService;

public class X_Reflect {

  private X_Reflect() {}
  
  //We have to put our mainly gwt-based reflection library in the main branch,
  //as shared code may need to be gwt-proofed.

  //As such, if you wish to use the reflection service without injection,
  //You must manually call GWT.create to get a JreReflectionService object
  //that you can use without this wrapper class
  public static final Provider singleton =
    X_Inject.singletonLazy(ReflectionService.class);

  public static  T[] newArray(Class classLit, int length){
    return singleton.get().newArray(classLit, length);
  }

  /**
   * This is an unfortunate workaround for gwt-dev mode's isolated
   * classloader not returning packages.
   *
   * If you use super dev mode instead of dev mode, you'll never need this
   * method.  If you do use dev mode, you should route all Class.getPackage()
   * through this method, which uses the thread classloader to get a regular
   * jre class (one that will cause ClassCastException if used reflectively!).
   *
   * This method can be of limited use for production mode; it will return a
   * package for a class completely lacking in package based annotations.
   *
   * @param classLit
   * @return
   */
  public static Package getPackage(Class classLit) {
    return singleton.get().getPackage(classLit);
  }

  /**
   * In order to selectively enable full class support in gwt,
   * we need to be able to see the class literal in the generator.
   *
   * You MUST only send class literals to this method;
   * Class<MyClass> cls = X_Reflect.magicClass(MyClass.class);
   *
   * Now you may use cls like any other class, to the extent provided by MagicClass,
   * and you may pass the variable around and use references to it in other X_Inject methods.
   * GWT.create() does not support magic classes, as we don't want to rewrite that method for anyone.
   * Use X_Inject.instance(), and it will default to GWT.create().
   * If you do use @InstanceOverride to inject a different class, it will also be instantiated w/ GWT.create().
   *
   * This method will call into a magic-method generator,
   * which pulls in all the required metadata at compile time,
   * and emits a "subclass" of java.lang.Class.
   *
   * This is completely illegal in java, but gwt is js, so anything goes.
   *
   * Rather than glob up a bunch of metadata into all class literals,
   * and cause terrible bloat across the app,
   * this method lets you select which classes you want full metadata on,
   * and which others will reduce to the typical, mostly-unsupported emulated Class.
   *
   * Note that for your gwt app to compile with references to the mostly unsupported class objects,
   * you must have xapi-super above gwt-user and gwt-dev on your classpath.
   * Our emulated class provides the method stubs, which throw exceptions to wrap objects w/ #magicClass.
   *
   *
   *
   * @param cls
   * @return
   */
  public static  Class magicClass(Class cls) {
    return singleton.get().magicClass(cls);
  }

  public static Package getPackage(String parentName, ClassLoader cl) {
    return singleton.get().getPackage(parentName, cl);
  }

}