Help!!! Sending serialized object to another server/servlet

Question

I am trying to simply send a serialized bean to a servlet on another server. I have lot's of examples of doing this as a stream and recieving back a stream to output, trouble is, I want to do this as a means of communicating the state of a process from one application kicking off the process on the new application. So when the page is returned, I need to be located on the new server. Here is the stream code I'm using:
String strUrl = "http://www.myurl.net";
try {
     URL url = new URL(strUrl);
     HttpMessage msg = new HttpMessage(url);
     BufferedReader in;
     Object beanObj = (Object) myBean;
     MyBean beany = (MyBean) beanObj;
     in = new BufferedReader(new InputStreamReader(msg.sendPostMessage(beany)));
     String inputLine;
     while ((inputLine = in.readLine()) != null) {
     out.println(inputLine + "\n");
     in.close();
catch(IOException io) {
out.println("Unable to call the servlet " + io);
out.close();
How would I do this if I wanted to send and not come back to the original server?

Answer 1

Why not create a little daemon to run on Server B (using the Servlet API would make this really easy) that listens for requests from Server A. The Servlet running on Server A would:
1. Do whatever it needs to do
2. Open an HttpURLConnection to Server B, use the getOutputStream() method to get a pipe to write serialized data to, couple it with an ObjectOutputStream, and write the session object to it.
3. Use the sendRedirect() method to redirect the client to Server B.
Upon receiving a request, the Servlet on Server B would:
1. Call Servlet.getInputStream() to get the input stream to read objects from.
2. Couple this with an ObjectInputStream to read objects from.
3. Read the session object and cast it to the appropriate type.
4. Stash the session object in a global lookup so it can be retrieved when the client arrives. I don't think the session can be created at this point because the request doesn't originate from the browser.
Then, finally, the Servlet running on Server B that handles client requests would:
1. Create a new session
2. Retrieve the session object from the global data store and stash it in session.
3. Go on its merry way.
Hope this was on target and is useful.