Example usage for org.objectweb.asm Opcodes interface-usage

Introduction

In this page you can find the example usage for org.objectweb.asm Opcodes interface-usage.

Usage

From source file org.evosuite.junit.writer.TestSuiteWriter.java

/**
 * Class used to generate the source code of the JUnit test cases.
 * <p/>
 * <p/>
 * NOTE: a test case should only access to the following packages
 * <ul>

From source file org.fabric3.binding.ws.metro.generator.java.codegen.InterfaceFromWsdlGeneratorImpl.java

/**
 *
 */
@Service(InterfaceFromWsdlGenerator.class)
public class InterfaceFromWsdlGeneratorImpl implements InterfaceFromWsdlGenerator, Opcodes {
    private static final String SUFFIX = "F3Subtype";

From source file org.fabric3.binding.ws.metro.generator.java.codegen.InterfaceGeneratorImpl.java

/**
 * Default implementation of InterfaceGenerator that uses ASM to generate a subclass of the original type with JAX-WS annotations.
 */
@Service(InterfaceGenerator.class)
public class InterfaceGeneratorImpl implements InterfaceGenerator, Opcodes {
    private static final String SUFFIX = "F3Subtype";

From source file org.fabric3.monitor.impl.proxy.BytecodeMonitorProxyService.java

/**
 * Performs bytecode generation at runtime to create a monitor proxy.
 * <p/>
 * The monitor proxy avoids object creation such as auto-boxing and varargs for highly performant environments. This is done by dynamically generating
 * writeParameters method with a specific number of arguments for each proxy interface method. The implementation of the proxy interface method invokes this
 * writeParameters method. Performance characteristics should therefore be the same as hand-implementing the proxy interface.

From source file org.fluidity.composition.maven.AbstractAnnotationProcessorMojo.java

/**
 * Mojos that find in a bunch of class files all implementations of a service provider interface, create a service provider file as per the JAR file
 * specification, find all components, generate a package bindings class for each and add these package bindings as service provider descriptor files.
 * <p>
 * Subclasses should call {@link AbstractAnnotationProcessorMojo#processDirectory(java.io.File, java.io.File...)} with the directory containing the classes to
 * process. The Maven build object can be obtained by calling {@link AbstractAnnotationProcessorMojo#build()}.

From source file org.fluidity.deployment.maven.ClassReaders.java

/**
 * Class related convenience methods.
 *
 * @author Tibor Varga
 */
public final class ClassReaders extends Utility implements Opcodes {

From source file org.graalvm.compiler.core.test.CustomizedBytecodePatternTest.java

public abstract class CustomizedBytecodePatternTest extends GraalCompilerTest implements Opcodes {

    protected Class<?> getClass(String className) throws ClassNotFoundException {
        return new CachedLoader(CustomizedBytecodePatternTest.class.getClassLoader(), className)
                .findClass(className);
    }

From source file org.graalvm.compiler.core.test.SubWordTestUtil.java

public final class SubWordTestUtil implements Opcodes {

    private SubWordTestUtil() {
    }

    static void convertToKind(MethodVisitor snippet, JavaKind kind) {

From source file org.gradle.language.base.internal.tasks.apigen.StubClassWriter.java

public class StubClassWriter extends ClassVisitor implements Opcodes {

    public static final String UOE_METHOD = "$unsupportedOpEx";
    private String internalClassName;

    public StubClassWriter(ClassWriter cv) {

From source file org.jboss.byteman.agent.adapter.OpcodesHelper.java

public class OpcodesHelper implements Opcodes {
    /**
     * instruction type for visitInsn opcodes
     */
    public final static int INSN_NONE = 0;
    /**