Problems with (JSP+CORBA+Websphere)

[pujji]

Hi everyone,
I'm new to websphere, I need to call CORBA objects from JSP in websphere.
Please explain the issues behind the architecture having JSPs (for user interface presentation) calling methods of CORBA objects deployed on WAS in an internet application. My requiremnet is CORBA objects for business logic and WAS as application server. This is must and can not be avoided. I am totally confused about -
1. How will JSP access the CORBA object?
2. Will there be a servlet in between necessarily? Personally I want to avoid servlet in this scenario because I believe both are capable of delivering same objectives. 3. What is the role of WAS in this scenario?
4. How the component broker comes into the picture and how it is integrated with WAS?
5. Can I deploy CORBA object to WAS3.5 or WAS4.0 advance edition?
6. How CORBA objects are deployed in WAS?
7. Will I get the WAS services such as transaction managemnt, object pooling, connection pooling, persistence, naming etc for CORBA objects. As WAS provides these services for EJBs.
8. When is WAS4.0 enterprise edition being released?

This is very lengthy question, but I need to explain what exactly I need. Thanks in advance

Pujji

 

[wushutwist]

First off I would like to make the suggestion that you use EJB instead of CORBA. There are many very good arguments against CORBA, but I won't waste your time right now because you seem to be locked into using CORBA.

1. Yes, you can access CORBA objects from JSP. No, I don't recommend it.

2. No, a Servlet is not absolutely necessary but I highly recommend using a Servlet as a sort of Traffic Cop. Are you familiar with the Model-View-Controller Pattern? It works very well with J2EE. A good design is to use EJB (CORBA in your case) as the Model, JSP as the View, and Servlets as the Controller. Using this Pattern JSP are deregulated to nothing more than Presentation Containers (like they should be) and all the real work it done using Servlets and Action or Command Classes.

3. WebSphere will be your Servlet/JSP Engine. Kinda of pricey to go with WebSphere just to do this but it does not support CORBA so that will be its only role in your scenario.

4. Your ORB will have to be a separate Server and there will be no integration to speak of.

5. You can't deploy CORBA based objects to WebSphere.

6. See 3 and 5.

7. See 3 and 5.

8. Check IBM's site. I have no clue.

Lastly as far as how to access CORBA objects from Java, you will need to use Java IDL (Interface Definition Language). There is really too much to go into here but if you really need this skill then I suggest you get sent to some training. In the meantime here is a link that will get you started:

http://java.sun.com/products/jdk/1.2/docs/guide/idl/jidlUsingCORBA.html.

Like many things in Java, CORBA is only difficult when you don't know how to do it. Wushutwist

 

[wushutwist]

The forum software kind of messed up the link. Here it is again:

http://java.sun.com/products/jdk/1.2/docs/guide/idl/jidlUsingCORBA.html

Wushutwist