We have this standalone application that uses HttpClient to download data from web and put them in database. The HttpClient is created with a MultiThreadedHttpConnectionManager, i.e., there are multiple threads managed by HttpClient downloading data concurrently.
Now we are asked to re-implement the logic in EJBs. Obviously, we cannot continue to use the MultiThreadedHttpConnectionManager because of the J2EE multi-threading limitation. We are planning to simulate the behavior by making multiple invocations from a servlet to the session bean that drives HttpClient in single thread mode. Does this sound like a viable solution?