An in-depth understanding of Java technology EJB call principle Analysis Two

A stub class ((Hello Bean)) of the WebLogic implementation class of the Home interface _homeimpl_wlstub (dynamically generated bytecode when deployed)

The Skeleton Class ((Hello Bean)) of the WebLogic implementation class of the Home interface _homeimpl_wlskeleton (dynamically generating bytecode when deployed)

Remote interface: Hello (user written)

Remote interface WebLogic Implementation class ((Hello Bean)) _eoimpl (EJBC generated)

A stub class ((Hello Bean)) of the WebLogic implementation class of the remote interface _eoimpl_wlstub (dynamically generated bytecode when deployed)

The Skeleton Class ((Hello Bean)) of the WebLogic implementation class of the remote interface _eoimpl_wlskeleton (dynamically generating bytecode when deployed)

The client only needs the two files Hello.class and Hellohome.class.

((Hello home)) Home = (home)

((Portable Remote Object). Narrow (Ctx.lookup ("Hello"),

((Hello Home)). Class);

This line of code is to get the home interface from Jndi, but keep in mind! The interface is abstract, so what exactly is the object instance of the Home object? Very simply, with the ToString () output to see that, the following line is the output result:

((Hello Bean)) _homeimpl_wlstub@18c458

This shows that the home this is actually an instance of the Hellobean_homeimpl_wlstub class by looking up the object obtained from the server's Jndi tree.

Next client code:

Hello h = home.create ()

Similarly, hello is just an abstract interface, so what is H object? Print:

((Hello Bean)) _eoimpl_wlstub@8fa0d1

The original is an object instance of Hellobean_eoimpl_wlstub.