Hi Prateek,
Before I try to give a qualified answer, can you clarify your situation as:
Tomcat 4.0.3 running the JSP & Servlets ->communicating IIOP ->W.L.6.1 SLSB
You mentioned that you are talking IIOP, is this pure IIOP ie. CORBA object to CORBA object or as I suspect RMI/IIOP?
My suggestion would be to produce a simple pure Java client that accesses the SLSB while talking ???/IIOP. Check your response regarding this procedure and then progress to embedding the Java logic into the Servlet.
Tomcat itself does not implement any of the RMI/IIOP specifications which can be found in the J2EE 2.6.4 section. You would have to be using the javax.rmi.* package if my understanding is correct.
cheers Luie
Prateek_Prakash <[EMAIL PROTECTED]> wrote:
Hi Friends,
We are facing problems communicating from an HTTP servlet to an EJB over IIOP. Hope someone can help.
The setup is something like this:
A swing client or standalone java client talks to the Webserver which in turn talks to the Session Facade EJB on the Weblogic server Version 6.1 sp2 on Solaris 8. Swing client is on a windows 2000 machine & all the code (EJBs, Servlets & client) are compiled with Windows JDK version 1.3.1_01. We are using EJB 2.0. The windows client talks with the Controller Servlet using Object Input & Output streams. An object array is passed from the client to the webserver which in turn passes it to the appserver. The webserver is Jakarta Tomcat 4.0.3 running on JDK1.3.1_04 on a Red Hat Linux 7.2 machine.
In Case 1, the object array contains objects which in turn contain an arraylist of objects.
In Case 2, the object array contains objects which do not contain any more arraylists of objects. All the objects & contained objects implement the Serializable interface. After looking up the EJB Home & getting the remote for the same a method is called & this Object array is passed to the called EJB method. In case 2, everything works perfectly & we get a proper response back. However in case 1, we get a marshalling/demarshalling error or an internal readObject error basically meaning that the EJB's method parameters were corrupted i.e. the Object array. On checking up the object array on the Controller Servlet on the webserver, it was found to be perfect. We are using the IIOP protocol from the servlet to the EJB. Both case 1 & case 2 are working with Standalone java clients talking directly to the EJB over the IIOP protocol.
Any solution or pointers on this would be highly appreciated.
TIA,
Prateek
==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
Yahoo! Digital How To - Get the best out of your PC!
