This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

doubt about a part 1 question

 
Along huang
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Heartbreak Hospital has two applications - Patient Registration System and Patient
Billing System. Patient Billing, an older application has CORBA interfaces for updating
Billing Information. The newer Patient Registration system was built as a Java based
Application. Heartbreak now wants to automatically update Billing Information from
the Patient Registration Application. What Java technology may be most suited for
this?(Select 1 correct choice)
a) RMI-JRMP
b) RMI-JNI
c) RMI-IIOP
d) EJB
e) Java IDL
f) Java-CORBA Bridge

Choice E is correct.

But I think that choice C is correct too. how do you think?
 
Manju Karthik
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

The Answer is correct. It is best to use Java IDL when Java System (Client) interfaces with CORBA system (Server). For other way around you can use RMI-IIOP.

Manju.
 
Gurumurthy Ramamurthy
Ranch Hand
Posts: 273
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The same doubt even I had. But later could manage:

1. CORBA is the billing system, so from Java how to connect to CORBA? best way is JAVA IDL.

2. RMI-IIOP is especially for EJBs. In our system, we don't rquire EJB at all, since EJB and RMI-IIOP are heavy-weight, so we can avoid this option.

Thanks,
Guru
 
Maneshi tuli
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Billing system in Corba. RMI-IIOP provides interoperability with other CORBA objects implemented in various languages - but only if all the remote interfaces are originally defined as Java RMI interfaces
Java IDL is for CORBA programmers who want to program in the Java programming language based on interfaces defined in CORBA Interface Definition Language (IDL).

So in this scenerio, its better to use Java IDL to communicate with Corba.
 
Yong How, Lim
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes... agreed with the above posts.

Since the questions says the new system has "Java based Application" (does not imply EJB) ... and the older system has "CORBA interfaces"

So the choice should be
"e) Java IDL"
 
Dan Drillich
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As Sun says at http://java.sun.com/products/jdk/idl -

Java IDL adds CORBA (Common Object Request Broker Architecture) capability to the Java platform, providing standards-based interoperability and connectivity. Java IDL enables distributed Web-enabled Java applications to transparently invoke operations on remote network services using the industry standard OMG IDL (Object Management Group Interface Definition Language) and IIOP (Internet Inter-ORB Protocol).


-- Dan
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic