Instead of serializing to XML and then parsing back to the bean, why not serialize using ObjectOutputStream to a byte and storing that in the database. I suspect it will be considerably faster since there will be no character conversions.
On your way in you may have missed that we have a policy on screen names here at JavaRanch. Basically, it must consist of a first name, a space, and a last name, and not be obviously fictitious. Since yours does not conform with it, please take a moment to change it, which you can do right here.
Converting a bean to XML format or object output stream and storing in DB for this is an overkill . What happens to this XML or object stream once other app has worked on the data . Unneccesary data in DB .
Some effective solutions are :- 1)Write the object stream of the object to be transfered on some socket on the other app and work from there . 2)Open a HTTPURLConnection to any servlet in other app and post the bean to that servlet . Read the bean there from object stream and work .
As you are not comfortable with TCP/Sockets use 2 . Any existing Servlet in other app can be used for this purpose . Just put an in condition to handle this case.
Joined: Sep 01, 2003
2)Open a HTTPURLConnection to any servlet in other app and post the bean to that servlet . Read the bean there from object stream and work .
Thats the data bit ok, but how would I then redirect them, so the new session they get in the second app has the bean we just posted?