There is a number of ways that CORBA objects can be accessed from web based applications.
(1)Java
applets can be downloaded via web based applications. These Java applets are capable of directly accessing CORBA objects via IIOP. There are a number of Java based ORBs available on the market. By introducing CORBA communication into a Java applet, arbitrary CORBA services can be accessed directly. These services can be developed in any language supported by CORBA or on top of any CORBA product that supports IIOP.
(2)A refinement of the above approach includes the various Web server extension technologies, such as
servlets, ASPs, JSPs, etc.
(3)Through CORBA,we can call objects through Dynamic method invocation ,where method name,return type and method arguments can be passed at runtime itself.
(4)Thru IDL(Interface definition language),CORBA is a platform independent and language independent technology.
EJB objects can be accessed thru CORBA clients,which EJB tech. supports IIOP.
EJB was developed relatively recently, well after CORBA had been through its early adoption pains. This gives CORBA a longer track record of successful and unsuccessful system installations. This, however, gives EJB the benefit of handsight. We have said that �EJB is CORBA combined with some best practices�. This is meant to indicate
At a high-level, EJB and CORBA are more similar than different.
The difficult architectural problems of distributed computing are still difficult, regardless of which technology is used. These problems reflect more on determining how the system should represent interfaces rather than how to act on those interfaces.
EJB provides some clarifying concepts. For example having two interface keywords, SessionBean and EntityBean, to indicate the conversational or non-conversational semantics of an object is useful. The same thing can be done with CORBA�s single style of interface, and most real CORBA systems distinguish between conversational and non-conversational interfaces.
Anil.
