org.apache.bcel.verifier
Class Verifier

java.lang.Object
  org.apache.bcel.verifier.Verifier

public class Verifier
extends Object

A Verifier instance is there to verify a class file according to The Java Virtual Machine Specification, 2nd Edition. Pass-3b-verification includes pass-3a-verification; pass-3a-verification includes pass-2-verification; pass-2-verification includes pass-1-verification. A Verifier creates PassVerifier instances to perform the actual verification. Verifier instances are usually generated by the VerifierFactory.

Version:

$Id: Verifier.java 386056 2006-03-15 11:31:56Z tcurdt $

Author:

Enver Haase

See Also:

VerifierFactory, PassVerifier

Field Summary

private String	classname The name of the class this verifier operates on.
private Pass1Verifier	p1v A Pass1Verifier for this Verifier instance.
private Pass2Verifier	p2v A Pass2Verifier for this Verifier instance.
private Map	p3avs The Pass3aVerifiers for this Verifier instance.
private Map	p3bvs The Pass3bVerifiers for this Verifier instance.

Constructor Summary

Verifier(String fully_qualified_classname)
Instantiation is done by the VerifierFactory.

Method Summary

VerificationResult	doPass1() Returns the VerificationResult for the given pass.
VerificationResult	doPass2() Returns the VerificationResult for the given pass.
VerificationResult	doPass3a(int method_no) Returns the VerificationResult for the given pass.
VerificationResult	doPass3b(int method_no) Returns the VerificationResult for the given pass.
void	flush() Forget everything known about the class file; that means, really start a new verification of a possibly different class file from BCEL's repository.
String	getClassName() Returns the name of the class this verifier operates on.
String[]	getMessages() This returns all the (warning) messages collected during verification.
static void	main(String[] args) Verifies class files.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

classname

private final String classname

The name of the class this verifier operates on.

p1v

private Pass1Verifier p1v

A Pass1Verifier for this Verifier instance.

p2v

private Pass2Verifier p2v

A Pass2Verifier for this Verifier instance.

p3avs

private Map p3avs

The Pass3aVerifiers for this Verifier instance. Key: Interned string specifying the method number.

p3bvs

private Map p3bvs

The Pass3bVerifiers for this Verifier instance. Key: Interned string specifying the method number.

Constructor Detail

Verifier

Verifier(String fully_qualified_classname)

Instantiation is done by the VerifierFactory.

See Also:

VerifierFactory

Method Detail

doPass1

public VerificationResult doPass1()

Returns the VerificationResult for the given pass.

doPass2

public VerificationResult doPass2()

Returns the VerificationResult for the given pass.

doPass3a

public VerificationResult doPass3a(int method_no)

Returns the VerificationResult for the given pass.

doPass3b

public VerificationResult doPass3b(int method_no)

Returns the VerificationResult for the given pass.

getClassName

public final String getClassName()

Returns the name of the class this verifier operates on. This is particularly interesting when this verifier was created recursively by another Verifier and you got a reference to this Verifier by the getVerifiers() method of the VerifierFactory.

See Also:

VerifierFactory

flush

public void flush()

Forget everything known about the class file; that means, really start a new verification of a possibly different class file from BCEL's repository.

getMessages

public String[] getMessages()
                     throws ClassNotFoundException

This returns all the (warning) messages collected during verification. A prefix shows from which verifying pass a message originates.

Throws:

ClassNotFoundException

main

public static void main(String[] args)

Verifies class files. This is a simple demonstration of how the API of BCEL's class file verifier "JustIce" may be used. You should supply command-line arguments which are fully qualified namea of the classes to verify. These class files must be somewhere in your CLASSPATH (refer to Sun's documentation for questions about this) or you must have put the classes into the BCEL Repository yourself (via 'addClass(JavaClass)').