I. Differences between dynamic proxy and static proxy. (1) The Proxy class code is fixed and won't be huge because of the increasing size of the business; (2) AOP programming can be implemented, which cannot be implemented by the static Proxy; (3) decoupling, for web services, you can separate the data layer from the business layer. (4) the advantage of dynamic proxy is non-intrusive code extension. The static proxy mode itself has a big problem. If the number of class methods is increasing, the amount of code for the proxy class is very large. Therefore, dynamic proxies are introduced to solve such problems.
Ii. Dynamic proxy
The key to implementing dynamic Proxy in Java is Proxy and InvocationHandler. The following describes how to implement dynamic Proxy in Java by starting with the invoke method in the InvocationHandler interface.
First, the complete form of the invoke method is as follows:
Java code
- Public Object invoke (Object proxy, Method method, Object [] args) throws Throwable
- {
-
- Method. invoke (obj, args );
-
- Return null;
- }
First, let's guess that method is the method called, that is, the method to be executed; args is the method parameter; proxy, what is this parameter? The above implementation of the invoke () method is a standard form. We can see that the proxy parameter is not used here. View the Proxy instructions in the JDK documentation as follows:
Java code
- A method invocation on a proxy instance through one of its proxy interfaces will be dispatched to the invoke method of the instance's invocation handler, passing the proxy instance, a java. lang. reflect. method object identifying the method that was invoked, and an array of type Object containing the arguments.
From this we can know that the above Guesses are correct, and we also know that the proxy parameter is passed to the proxy class instance.
For convenience, here is a simple example to implement dynamic proxy.
Java code
- // Abstract role (Dynamic proxy can only be a proxy Interface)
- Public interface Subject {
-
- Public void request ();
- }
Java code
- // Real role: implements the Subject request () method.
- Public class RealSubject implements Subject {
-
- Public void request (){
- System. out. println ("From real subject .");
- }
- }
Java code
- // Implements InvocationHandler
- Public class DynamicSubject implements InvocationHandler
- {
- Private Object obj; // This is the benefit of dynamic proxy. The encapsulated Object is of the Object type and can be any type of Object.
-
- Public DynamicSubject ()
- {
- }
-
- Public DynamicSubject (Object obj)
- {
- This. obj = obj;
- }
-
- // This method is not displayed for calling
- Public Object invoke (Object proxy, Method method, Object [] args) throws Throwable
- {
- System. out. println ("before calling" + method );
-
- Method. invoke (obj, args );
-
- System. out. println ("after calling" + method );
-
- Return null;
- }
-
- }
Java code
- // Client: generates a proxy instance and calls the request () method.
- Public class Client {
-
- Public static void main (String [] args) throws Throwable {
- // TODO Auto-generated method stub
-
- Subject rs = new RealSubject (); // The proxy class is specified here.
- InvocationHandler ds = new DynamicSubject (rs );
- Class Cls = rs. getClass ();
-
- // The following is a one-time generation Proxy:
-
- Subject subject = (Subject) Proxy. newProxyInstance (
- Cls. getClassLoader (), cls. getInterfaces (), ds );
-
- // The running result shows that the subject is an instance of the Proxy. This instance implements the Subject interface.
- System. out. println (subject instanceof Proxy );
-
- // Here we can see that the Class of subject is $ Proxy0. This $ Proxy0 Class inherits the Proxy and implements the Subject interface.
- System. out. println ("the Class of subject is:" + subject. getClass (). toString ());
-
- System. out. print ("attributes in subject are :");
-
- Field [] field = subject. getClass (). getDeclaredFields ();
- For (Field f: field ){
- System. out. print (f. getName () + ",");
- }
-
- System. out. print ("\ n" + "methods in subject include :");
-
- Method [] method = subject. getClass (). getDeclaredMethods ();
-
- For (Method m: method ){
- System. out. print (m. getName () + ",");
- }
-
- System. out. println ("\ n" + "subject's parent class is:" + subject. getClass (). getSuperclass ());
-
- System. out. print ("\ n" + "subject :");
-
- Class [] Interfaces = subject. getClass (). getInterfaces ();
-
- For (Class I: interfaces ){
- System. out. print (I. getName () + ",");
- }
-
- System. out. println ("\ n" + "running result :");
- Subject. request ();
- }
- }
Xml Code
- The running result is as follows: the package name is omitted here, which is replaced ***.
- True
- The subject Class is: class $ Proxy0
- Attributes in subject include m1, m3, m0, m2,
- Methods In subject include: request, hashCode, equals, toString,
- Subject's parent class is: class java. lang. reflect. Proxy
- The subject implementation interface is: cn.edu. ustc. dynamicproxy. Subject,
-
- The running result is:
- Before calling public abstract void ***. Subject. request ()
- From real subject.
- After calling public abstract void ***. Subject. request ()
PS: The result information is very important, at least for me. Because the root cause of my dizzy behavior on the dynamic proxy is to apply the above subject. the request () is wrong. At least it is confused by the surface. No connection is found between this subject and the Proxy. At one time, It is entangled in how the request () is called and invoke () contact, and how does invoke know that the request exists. In fact, the above true and class $ Proxy0 can solve a lot of questions, coupled with the $ Proxy0 source code to be discussed below, can completely solve the problem of dynamic proxy.
From the above Code and results, we can see that the invoke () method is not displayed, but this method is indeed executed. The entire process is analyzed as follows:
From the code in the Client, we can take the newProxyInstance method as a breakthrough. Let's take a look at the source code of the newProxyInstance method in the Proxy class:
Java code
- Public static Object newProxyInstance (ClassLoader loader,
- Class [] Interfaces,
- InvocationHandler h)
- Throws IllegalArgumentException
- {
- If (h = null ){
- Throw new NullPointerException ();
- }
-
- /*
- * Look up or generate the designated proxy class.
- */
- Class cl = getProxyClass (loader, interfaces );
-
- /*
- * Invoke its constructor with the designated invocation handler.
- */
- Try {
- /*
- * The Proxy source code is defined as follows:
- * Private final static Class [] constructorParams = {InvocationHandler. class };
- * Cons is the constructor of the InvocationHandler type.
- */
- Constructor cons = cl. getConstructor (constructorParams );
- Return (Object) cons. newInstance (new Object [] {h });
- } Catch (NoSuchMethodException e ){
- Throw new InternalError (e. toString ());
- } Catch (IllegalAccessException e ){
- Throw new InternalError (e. toString ());
- } Catch (InstantiationException e ){
- Throw new InternalError (e. toString ());
- } Catch (InvocationTargetException e ){
- Throw new InternalError (e. toString ());
- }
- }
Proxy. newProxyInstance (ClassLoader loader, Class [] Interfaces, InvocationHandler h) Does the following.
(1) create a Proxy class $ Proxy0. $ Proxy0 Class Based on the getProxyClass (loader, interfaces) Call methods of the loader and interfaces parameters to implement the interfaces interface and inherit the Proxy class.
(2) instantiate $ Proxy0 and pass DynamicSubject to the constructor In the constructor method. Then $ Proxy0 calls the constructor of the parent class Proxy and assigns a value to h, as shown below:
Java code
- Class Proxy {
- InvocationHandler h = null;
- Protected Proxy (InvocationHandler h ){
- This. h = h;
- }
- ...
- }
Let's take a look at the source code that inherits the $ Proxy0 of Proxy:
Java code
- Public final class $ Proxy0 extends Proxy implements Subject {
- Private static Method m1;
- Private static Method m0;
- Private static Method m3;
- Private static Method m2;
-
- Static {
- Try {
- M1 = Class. forName ("java. lang. Object"). getMethod ("equals ",
- New Class [] {Class. forName ("java. lang. Object ")});
-
- M0 = Class. forName ("java. lang. Object"). getMethod ("hashCode ",
- New Class [0]);
-
- M3 = Class. forName ("***. RealSubject"). getMethod ("request ",
- New Class [0]);
-
- M2 = Class. forName ("java. lang. Object"). getMethod ("toString ",
- New Class [0]);
-
- } Catch (NoSuchMethodException nosuchmethodexception ){
- Throw new NoSuchMethodError (nosuchmethodexception. getMessage ());
- } Catch (ClassNotFoundException classnotfoundexception ){
- Throw new NoClassDefFoundError (classnotfoundexception. getMessage ());
- }
- } // Static
-
- Public $ Proxy0 (InvocationHandler invocationhandler ){
- Super (invocationhandler );
- }
-
- @ Override
- Public final boolean equals (Object obj ){
- Try {
- Return (Boolean) super. h. invoke (this, m1, new Object [] {obj}). booleanValue ();
- } Catch (Throwable throwable ){
- Throw new UndeclaredThrowableException (throwable );
- }
- }
-
- @ Override
- Public final int hashCode (){
- Try {
- Return (Integer) super. h. invoke (this, m0, null). intValue ();
- } Catch (Throwable throwable ){
- Throw new UndeclaredThrowableException (throwable );
- }
- }
-
- Public final void request (){
- Try {
- Super. h. invoke (this, m3, null );
- Return;
- } Catch (Error e ){
- } Catch (Throwable throwable ){
- Throw new UndeclaredThrowableException (throwable );
- }
- }
-
- @ Override
- Public final String toString (){
- Try {
- Return (String) super. h. invoke (this, m2, null );
- } Catch (Throwable throwable ){
- Throw new UndeclaredThrowableException (throwable );
- }
- }
- }
Then, convert the obtained $ Proxy0 instance to Subject and assign the reference to subject. When subject. the request () method in the $ Proxy0 class is called, and the invoke () method of h in the parent class Proxy is called. that is, InvocationHandler. invoke ().
PS: 1. Note that the getProxyClass method in the Proxy Class returns the Proxy Class. The reason for this is that I first made a low-level error and thought that the returned Class was "Class under the proxy Class "--! It is recommended that you take a look at the source code of getProxyClass, which is very long =. =
2. From the source code of $ Proxy0, we can see that the dynamic proxy class not only proxy the methods in the display defined interface, but also proxies the inherited equals () in the java root class Object (), hashcode (), toString (), and only the three methods.
Q: so far, I have another question: the first parameter in the invoke method is the Proxy instance (to be precise, the $ Proxy0 instance is used in the end). But what is the purpose? In other words, how does one display the function in the program?
A: As far as my current level is concerned, this proxy parameter does not play A role. In the entire dynamic proxy mechanism, the proxy parameter of the InvocationHandler method is not used. The input parameter is actually an instance of the proxy class. I think it may be to allow programmers to use reflection in the invoke method to obtain some information about the proxy class.
