Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

about changing from rmi to corba  RSS feed

 
Kapil Keskar
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
If I wish to change my platform from RMI to CORBA what will be changes required for my SWING based project which i am doing it in SWING-RMI
I heard that I have to pay for ORB if i use CORBA. is it true?
if so how much?
Can anybody tell me about this?
Thanx
 
Simon Xu
Ranch Hand
Posts: 235
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Corba was hot during last two years, but now is cool down. Is it correct?
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Exactly what are the reasons why you want to move from RMI to CORBA?
Kyle
 
Michael Ernest
High Plains Drifter
Sheriff
Posts: 7292
Netbeans IDE VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If it's well-designed, the Swing/presentation portion of your application should be unaffected by your "choice" of CORBA or RMI as a network transport protocol.
The key difference between the two: CORBA assumes all platforms may wish to talk, and may be written in any language, so they need a neutral framework for understanding each other; RMI assumes all platforms may wish to talk, so they need a JVM for understanding each other.
RMI uses stubs to represent server objects in a remote context; CORBA uses its Interface Definition Language (IDL) to produce about the same kind of thing in a language-neutral form.
CORBA stuff should of course adhere to a known standard, but every vendor is free to determine how well or poorly they adhere to that standard and what bells and whistles they're going to add on top of it. CORBA is more complex (many people seem to mistake this for 'robustness'), and its expensive because there are few players in the field, the most eager customers have money to spend, and developing ORBs is not a cost-free proposition.
There is nothing you can accomplish in CORBA that you can't accomplish in RMI, so comparisons often boil down to stability, price/performance, ease of integration, etc. RMI can do one or two not-so little things that CORBA can't do (but does support in a Java/CORBA mix), but again you have to have JVM's everywhere.
So I'm with Kyle; if you started with CORBA and have to integrate some Java-made stuff that you've acquired, ok. But why would you want to change to CORBA with new stuff?
 
Kapil Keskar
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Though CORBA is not in much hype today it's very useful when to communicate with diff applications & different platforms.
so my point was that what exactly Micheal wrote that 'CORBA assumes all platforms may wish to talk, and may be written in any language, so they need a neutral framework for understanding each other; RMI assumes all platforms may wish to talk, so they need a JVM for understanding each other.'
so whenever there is no JVM, we cannot talk to another platform application. that's limitation.
that's why wanted.
so is there any replacement for RMI code.
Thanx
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!