The Artima Developer Community
Sponsored Link

Agile Buzz Forum
CORBA, WS*, and Confusion

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
CORBA, WS*, and Confusion Posted: Oct 3, 2005 6:52 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: CORBA, WS*, and Confusion
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

Patrick Logan points to a debate over CORBA and WS* between Roger Sessions and Terry Coatta over at ACM Queue. He points out some fun stuff, like this exchange here:

RS If you’re using the J2EE standards such as RMI (remote method invocation) over IIOP (Internet Inter-ORB Protocol), you are primarily going to be doing that within a single vendor’s system, such as a WebSphere system. If you’re going from a WebSphere system to a WebLogic system, your best shot at interoperability is through Web services. Why? Because you’re crossing a technology boundary.

TC You’re claiming that RMI over IIOP doesn’t actually work?

RS It doesn’t work for interoperability across technology boundaries.

TC

There seem to be people out there getting it to work. Certainly, back in the days when I worked with CORBA there was no problem having different vendors’ ORBs (object request brokers) interoperate with one another. We used three or four of them at Open Text and had no difficulty at all with those environments interoperating with one another.

RS As long as you’re going CORBA to CORBA, it works fine. But not when you are trying to get a CORBA system to work with a non-CORBA system.

TC But going from WebSphere to one of the other EJB vendors (e.g., WebLogic) in the CORBA space, there were probably five or six different major ORB vendors floating around, not to mention a couple of open source efforts, and all of those interoperated really well with one another.

RS CORBA to CORBA. They’re all running on the same basic core of CORBA technology. The difference between that and Web services is that for Web services, unlike CORBA, there is no assumption whatsoever about what the underlying technology is.

Yes, one CORBA end point only works with another CORBA end point. Does that mean that Sessions believes that WS* works differently? Can I send a plain text (as opposed to XML) document via FTP to a WS* server listening via HTTP? What point is Sessions trying to make here? WS* is no more or less interoperable than CORBA was. The difference? The fact that most web services run via HTTP (and thus, via port 80) - so they can move between firewalls. With CORBA, you have to get IT (or IT security) to open up a port in the firewall (on both ends). The usage of HTTP as a transport gets around that problem.

That's really the only difference between the two at the 50,000 foot level. Lower down, of course, WS* manages to be even more complex (as Patrick points out). Managing to be more complex than CORBA is a rare achievement.

Read: CORBA, WS*, and Confusion

Topic: The value of unit tests Previous Topic   Next Topic Topic: An evening of good news

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use