This is NOT part of any supported API. If you write code that depends on this, you do so at your own risk. This code and its internal interfaces are subject to change or deletion without notice.
The signature algorithm can be, among others, the NIST standard DSA, using DSA and SHA-1. The DSA algorithm using the SHA-1 message digest algorithm can be specified as SHA1withDSA. In the case of RSA, there are multiple choices for the message digest algorithm, so the signing algorithm could be specified as, for example, MD2withRSA, MD5withRSA, or SHA1withRSA. The algorithm name must be specified, as there is no default.
A Signature object can be used to generate and verify digital signatures.
There are three phases to the use of a Signature object for either signing data or verifying a signature:
Depending on the type of initialization, this will update the bytes to be signed or verified. See the {@link #update(byte) update} methods.
Note that this class is abstract and extends from SignatureSpi for historical reasons. Application developers should only take notice of the methods defined in this Signature class; all the methods in the superclass are intended for cryptographic service providers who wish to supply their own implementations of digital signature algorithms.
@author Benjamin Renaud
@version 1.103, 04/21/06
Zephyr Business Solution @author Ben Yu
Represents the signature at a join point. This interface parallels java.lang.reflect.Member.
This interface is typically used for tracing or logging applications to obtain reflective information about the join point, i.e. using the j2se 1.4 java.util.logging API
aspect Logging { Logger logger = Logger.getLogger("MethodEntries"); before(): within(com.bigboxco..*) && execution(public * *(..)) { Signature sig = thisJoinPoint.getSignature(); logger.entering(sig.getDeclaringType().getName(), sig.getName()); } } More detailed information about a specific kind of signature can be obtained by casting this Signature object into one of its more specific sub-types available in org.aspectj.lang.reflect.
@see java.lang.reflect.Member
@see java.util.logging.Logger
A BEL function signature has the following format:
A([arg1,arg2,...,argN {@code [...]}])B where A is a BEL function enum and B is a BEL return type. The following rules concerning arguments are: F:Awhere A is a return type. Or in the second format:
E:Bwhere B is a value encoding. In both cases, what comes after the colon defines what is a valid parameter at that position in the function. @see FunctionEnum BEL function definitions @see ReturnType BEL function return types @see ValueEncoding BEL function parameter encodings
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |