假定我们要创建一个读取User信息的SessionBean,需要我们写的有3个文件:
1. UserServiceHome.java
Home接口
2. UserService.java
Remote接口
3. UserServiceBean.java
Bean实现
WSAD最终会生成10个class。其它7个是什么呢?我们一个一个数过来:
4. _UserServiceHome_Stub.java
这个当然就是Home接口在Client端(动态加载)的Stub类了,它implements UserServiceHome。
5. _EJSRemoteStatelessUserServiceHome_a940aa04_Tie.java
Home接口在Server端的Skeleton类,"a940aa04"应该是随机生成的,所有其他的相关class名里都会有这个标志串,Tie是Corba对Skeleton的叫法。
6. EJSRemoteStatelessUserServiceHome_a940aa04.java
Home接口在Server端的实现,当然,它也implements UserServiceHome。
7. EJSStatelessUserServiceHomeBean_a940aa04.java
由#6调用,create _UserService_Stub。(为什么#6不能直接create _UserService_Stub呢?后面再讲。)
8. _UserService_Stub.java
Remote接口在Client端(动态加载)的Stub类。它implements UserService。
9. _EJSRemoteStatelessUserService_a940aa04_Tie.java
Remote接口在Server端的Skeleton类。
10. EJSRemoteStatelessUserService_a940aa04.java
Remote接口在Server端的实现,当然,它也implements UserService。并且,它负责调用UserServiceBean——也就是我们所写的Bean实现类——里面的business method。
那么,各个类之间的调用关系到底是怎么样的呢?简单的说,就是两次RMI循环
先来看看Client端的程序是怎么写的:
- try {
- InitialContext ctx = new InitialContext();;
- //第一步
- UserServiceHome home =
- (UserServiceHome); PortableRemoteObject.narrow(
- ctx.lookup(JNDIString);,
- UserServiceHome.class);;
- //home: _UserServiceHome_Stub
- System.out.println(home.toString(););;
- //第二步
- UserService object = home.create();;
- //ojbect: _UserService_Stub
- System.out.println(object.toString(););;
- //第三步
- int userId = 1;
- UserInfo ui = object.getUserInfo(userId);;
- }
try {
InitialContext ctx = new InitialContext();;
//第一步
UserServiceHome home =
(UserServiceHome); PortableRemoteObject.narrow(
ctx.lookup(JNDIString);,
UserServiceHome.class);;
//home: _UserServiceHome_Stub
System.out.println(home.toString(););;
//第二步
UserService object = home.create();;
//ojbect: _UserService_Stub
System.out.println(object.toString(););;
//第三步
int userId = 1;
UserInfo ui = object.getUserInfo(userId);;
}
在第一步之后,我们得到了一个UserServiceHome(interface)定义的对象home,那么,home到底是哪个class的instance呢?用debug看一下,知道了home原来就是_UserServiceHome_Stub的实例。
从第二步开始,就是我们的关注所在,虽然只有简单的一行代码,
UserService object = home.create();
但是他背后的系统是怎么运做的呢?我们进入代码来看吧:
1. 调用home.create()
- UserServiceHome home;
- UserService obj = home.create();;
UserServiceHome home;
UserService obj = home.create();;
2. 实际是调用_UserServiceHome_Stub.create(),在这个方法里面,Stub向Skeleton发送了一个create的字串:
- org.omg.CORBA.portable.OutputStream out = _request("create", true);;
- in = (org.omg.CORBA_2_3.portable.InputStream);_invoke(out);;
org.omg.CORBA.portable.OutputStream out = _request("create", true);;
in = (org.omg.CORBA_2_3.portable.InputStream);_invoke(out);;
3. Server端的Skeleton接收Stub发来的request,并调用相应的方法:
- _EJSRemoteStatelessUserServiceHome_a940aa04_Tie._invoke(); {
- ......
- switch (method.length();); {
- case 6:
- if (method.equals("create");); {
- return create(in, reply);;
- }
- ......
- }
- }
_EJSRemoteStatelessUserServiceHome_a940aa04_Tie._invoke(); {
......
switch (method.length();); {
case 6:
if (method.equals("create");); {
return create(in, reply);;
}
......
}
}
- _EJSRemoteStatelessUserServiceHome_a940aa04_Tie.create(); {
- EJSRemoteStatelessUserServiceHome_a940aa04 target = null;
- result = target.create();;
- org.omg.CORBA.portable.OutputStream out = reply.createReply();;
- Util.writeRemoteObject(out,result);;
- return out;
- }
_EJSRemoteStatelessUserServiceHome_a940aa04_Tie.create(); {
EJSRemoteStatelessUserServiceHome_a940aa04 target = null;
result = target.create();;
org.omg.CORBA.portable.OutputStream out = reply.createReply();;
Util.writeRemoteObject(out,result);;
return out;
}
4. Skeleton调用的是UserServiceHome的Server端实现类的create方法
- EJSRemoteStatelessUserServiceHome_a940aa04.create(); {
- UserService _EJS_result;
- _EJS_result = EJSStatelessUserServiceHomeBean_a940aa04.create();;
- }
EJSRemoteStatelessUserServiceHome_a940aa04.create(); {
UserService _EJS_result;
_EJS_result = EJSStatelessUserServiceHomeBean_a940aa04.create();;
}
5. #4又调用EJSStatelessUserServiceHomeBean_a940aa04.create()
- UserService result = super.createWrapper(new BeanId(this, null););;
UserService result = super.createWrapper(new BeanId(this, null););;
至此,我们终于结束了第一个RMI循环,并得到了Remote接口UserService的Stub类_UserService_Stub,就是#5里面的result。
这里有一个问题,为什么#4不直接create _UserService_Stub,而又转了一道#5的手呢?因为#4 extends from EJSWrapper,它没有能力create Stub,因此必须借助#5,which extends from EJSHome,这样才可以生成一个Stub。如果不是为了生成这个Stub,应该可以不走#5这一步。
现在我们的Client端走到第三步了:
UserInfo ui = object.getUserInfo(userId);
继续看代码,开始第二个RMI循环:
1. 调用object.getUserInfo()
- UserService object;
- object.getUserInfo(userId);;
UserService object;
object.getUserInfo(userId);;
2. 实际是调用_UserService_Stub.getUserInfo(int arg0),在这个方法里面,Stub向Skeleton发送了一个getUserInfo的字串和arg0这个参数:
- org.omg.CORBA.portable.OutputStream out = _request("getUserInfo", true);;
- out.write_long(arg0);;
- in = (org.omg.CORBA_2_3.portable.InputStream);_invoke(out);;
org.omg.CORBA.portable.OutputStream out = _request("getUserInfo", true);;
out.write_long(arg0);;
in = (org.omg.CORBA_2_3.portable.InputStream);_invoke(out);;
3. Server端的Skeleton接收Stub发来的request,并调用相应的方法:
- _EJSRemoteStatelessUserService_a940aa04_Tie._invoke(); {
- switch (method.charAt(5););
- {
- case 83:
- if (method.equals("getUserInfo");); {
- return getUserInfo(in, reply);;
- }
- ......
- }
- }
- _EJSRemoteStatelessUserService_a940aa04_Tie.getUserInfo(); {
- EJSRemoteStatelessUserService_a940aa04 target = null;
- int arg0 = in.read_long();;
- UserDTO result = target.getUserInfo(arg0);;
- org.omg.CORBA_2_3.portable.OutputStream out = reply.createReply();;
- out.write_value(result,UserDTO.class);;
- return out;
- }
_EJSRemoteStatelessUserService_a940aa04_Tie._invoke(); {
switch (method.charAt(5););
{
case 83:
if (method.equals("getUserInfo");); {
return getUserInfo(in, reply);;
}
......
}
}
_EJSRemoteStatelessUserService_a940aa04_Tie.getUserInfo(); {
EJSRemoteStatelessUserService_a940aa04 target = null;
int arg0 = in.read_long();;
UserDTO result = target.getUserInfo(arg0);;
org.omg.CORBA_2_3.portable.OutputStream out = reply.createReply();;
out.write_value(result,UserDTO.class);;
return out;
}
4. Skeleton调用的是UserService的Server端实现类的getUserInfo方法
- EJSRemoteStatelessUserService_a940aa04.getUserInfo(); {
- UserServiceBean _EJS_beanRef = container.preInvoke(this, 0, _EJS_s);;
- _EJS_result = _EJS_beanRef.getUserInfo(id);;
- }
EJSRemoteStatelessUserService_a940aa04.getUserInfo(); {
UserServiceBean _EJS_beanRef = container.preInvoke(this, 0, _EJS_s);;
_EJS_result = _EJS_beanRef.getUserInfo(id);;
}
最后的最后,#4终于调用了我们写的UserServiceBean里的getUserInfo方法,这才是我们真正想要去做的事情。
至此,第二个RMI循环也终于结束了。