w**********k
发帖数: 1135 | 1 The EJB specification mandates that you must use the RMI interfaces to
communicate with an EJB component. The EJB specification does not
mandate which wire protocol (like CORBAs IIOP) to use. If you were to
build an EJB server on top of CORBA, using RMI/IIOP would be a natural
fit. |
|
j*****I
发帖数: 2626 | 2 看过一本M$介绍WCF的书，提到service-orientation跟CORBA有关，给我的印象就是
CORBA是个过
季的东西。而这个IIOP又是CORBA的重要部分。那么，是不是IIOP也过季了呢? 或者这
个IIOP已经
是个实际的industry standard,已经成为SOA的一部分，只是不提而已?
being |
|
g*****g
发帖数: 34805 | 3 SOA works on top of services, it doesn't concern how services are
implemented. RMI is a protocol to implement service, RMI can run on
top of IIOP but that's not the only way to do it. IIOP is a lower
level protocol.
Overall, if you are learning SOA, IIOP is not your concern. |
|
w**********k
发帖数: 1135 | 4 The Enterprise JavaBeans specification is intended to support compliance
with the range of CORBA standards, current and proposed.
A Bean's remote and home interfaces are RMI compliant, and thus
can interact with CORBA objects via RMI/IIOP, Sun and IBM's
forthcoming adaptation of RMI that conforms with the
CORBA-standard IIOP protocol.
As a companion to the Enterprise JavaBeans specification, Sun
Microsystems has defined a standard mapping from Enterprise Java
Beans API to CORBA IDL.
JTA, the tra |
|
z****u
发帖数: 15 | 5 EJB and Corba are merging together. It was described as a "shotgun marriage".
Both EJB and Corba are now supported in major application servers.
I don't remember what exactly happens but EJB is using Corba IIOP (RMI over
IIOP) as its communication protocol and Corba also benefits from some features
in Java. |
|
z*******3
发帖数: 13709 | 6 你们才是大牛，我是凑热闹的
我觉得thin client说的是html的那个browser
thick client是游戏客户端这种
当然ejb本身也可以作为ejb的client
这也不稀奇，只要对方有jvm，就可以被调用
rmi是底层的java实现，只要有java的地方，就可以实现rmi
但是rmi不好用，ejb的remote接口在rmi-iiop上实现了一层封装
好很多了
同时从另外一个角度说，web service虽然最早源起于web
但是应用在web server和app server的通信上也不是不可以
而且理论上效率不应该太差
因为rest是在tcp之上用http实现request,用xml封装response
而传统的rmi是在tcp之上用iiop实现request和response
再用serializable实现不同jvm上的类重现
唯一的区别就在于，rest需要用xml解码，把类里面的value给提取出来
其实这两个都是用tcp协议，实际传送的都是io stream
然后再从stream到具体的class，不应该有太大差距
所以只要这个网络条件相同，rmi，ejb的... 阅读全帖 |
|
o*b
发帖数: 42 | 7 Just a few days ago oas 4082 was in production. But I would strongly recommend
you to use oas 4081 which I think is the stablest version I've seen.
OAS is a Web server and if you want this web server to have db activities,
you certainly need 8i as the db backend. If your web site does not need
to handle db data, OAS is enough. But that is a rare case.
Oracle 8i has an internal IIOP listener and embedded JVM which can run stored
Java procedure, corba server, EJB and right now, it is upgraded t |
|
l**e
发帖数: 97 | 8 How about one-way function? Is that based on TCP also?
Is IIOP/TCP one-connection-per-request, or one-connection-per-client,
or one-connection-per-proxy-object, or ...?
//thx |
|
f*****c
发帖数: 22 | 9 I think it is up to the vendor to choose TCP or UDP as the implementation
of IIOP as long as CORBA do not specify it(I do not know such specification).
Of couse, even if you arre using UDP, you still have to come up with a
protocol to ensure that your packet will be correctly received at the other
end.
So it is also true about one-way function.
As for the pooling mode, it SHOULD be adjustable for individual CORBA products
I once used Visibroker and it can be specified via a method of boa. |
|
r***l
发帖数: 67 | 10 Java supports CORBA through two ways:
1. Java IDL
2. RMI/IIOP
You can use either way to implement both the server and the clients. Client
always talk (RPC call) to the server first and register themselves. Sever can
expose a find function for the client to call and find other client. After
clients find each other, they can get connection information for each other
through the server registry and start chatting (RPC calls).
That
two
with |
|
s***8
发帖数: 1136 | 11 can be used in any java-to-java distributed apps, ejb (using rmi-iiop) being
one of them. |
|
x*******i
发帖数: 777 | 12 1.你需要精通面向对象分析与设计(OOA/OOD)、涉及模式(GOF，J2EEDP)以及综合模式。你
应该十分了解UML，尤其是class，object，interaction以及statediagrams。
2.你需要学习JAVA语言的基础知识以及它的核心类库 (collections，
serialization
，streams，networking， multithreading，reflection，event，handling，
NIO，
localization，以及其他)。
3.你应该了解JVM，classloaders，classreflect，以及垃圾回收的基本工作机制
等。
你应该有能力反编译一个类文件并且明白一些基本的汇编指令。
4.如果你将要写客户端程序，你需要学习WEB的小应用程序(applet)，必需掌握GUI设
计的思想和方法，以及桌面程序的 SWING，AWT， SWT。你还应该对UI部件的
JAVABEAN组
件模式有所了解。JAVABEANS也被应用在JSP中以把业务逻辑从表现层中分离出来。
5.你需要学习j... 阅读全帖 |
|
x*******i
发帖数: 777 | 13 1.你需要精通面向对象分析与设计(OOA/OOD)、涉及模式(GOF，J2EEDP)以及综合模式。你
应该十分了解UML，尤其是class，object，interaction以及statediagrams。
2.你需要学习JAVA语言的基础知识以及它的核心类库 (collections，
serialization
，streams，networking， multithreading，reflection，event，handling，
NIO，
localization，以及其他)。
3.你应该了解JVM，classloaders，classreflect，以及垃圾回收的基本工作机制
等。
你应该有能力反编译一个类文件并且明白一些基本的汇编指令。
4.如果你将要写客户端程序，你需要学习WEB的小应用程序(applet)，必需掌握GUI设
计的思想和方法，以及桌面程序的 SWING，AWT， SWT。你还应该对UI部件的
JAVABEAN组
件模式有所了解。JAVABEANS也被应用在JSP中以把业务逻辑从表现层中分离出来。
5.你需要学习j... 阅读全帖 |
|
z*******3
发帖数: 13709 | 14 persession可不是stateful
persession是spring里面web的scope=session
percall是spring里面web的scope=request
singleton是常用模式，并不是只有business tier才有
我这里说的跟.net没有必然联系
今天稍微快速扫了一下.net
发现没有business tier这个概念
你还在尝试用web层的概念去理解business tier的东西
这会出问题的，而且business tier本身有很多讲究
等下我再展开，其实web service是web层也就是presentation的概念
以前ejb时代，presentation tier和business tier用的是iiop协议
至于rest的推广是我的个人的一个观点，并不代表一定可行
但是我认为将来这么做是有可能的 |
|
z****e
发帖数: 54598 | 15 你这个integration是db那一层还是系统集成？
front end跟client的打交道就是xhtml啊
然后hibernate跟db的处理，可以通过建立连接池来优化
而且db跟java的衔接在tcp协议上已经比较成熟了
所以这一层反而可以不要xml
现在唯一的问题就是ejb这一层跟web server之间的通信
只要效率接近，没有理由不上xml
而iiop跟http本身都是建立在tcp上的连接
无非就是虚拟机转换xml这种东西效率的问题
我个人感觉，这种差距不应该太大，而效率上如果差距被缩小
那么xml显然是一个更好的解决方案，而非rmi
实际上这么多年，rmi并不是很成功，倒是xml有愈烧愈旺之势
bpel是有局限，本身是工作流的升级，所以有
bpel vs esb一说，看情况决定整体结构
remote |
|
F****n
发帖数: 3271 | 16 That's why you don't use wiki as the only reliable source of info
SOAP is successor of XML-RPC, it can be used without WSDL, e.g., to replace
Java RMI-IIOP, which is usually blocked by firewall.
In fact my first SOAP application was to replace a RMI rather than to build
a Web Service (although you can call it a "web service" if you like).
of |
|
