In big enterprises everything is not controlled by one group. There will be a big legacy out there. It is not just one or two webservices you call to get the data. In our case, we had call around 12 webservices. Whatever kind of optimization you do, it is difficult to beat what we can get out of threading. I totally understand he multithreading is not allowed by servlet specification, but we didn't had an option but to use it. Rgds,
Satya On Mon, May 18, 2009 at 12:46 AM, Lukasz Lenart < lukasz.len...@googlemail.com> wrote: > 2009/5/17 sid5 <siddharthchha...@hotmail.com>: > > We currently have a SOA based application with a struts front end. > > We have to invoke multiple webservices to get the data to render a single > > page. > > I was thinking of writing an Executor service inside an Action class or > an > > Interceptor to do this. > > Is this the right approach ? > > It's no so good to mess with threads on application server, as I > remember it's not allowed by servlet specification, you should use > given servlet specific approach. > > > I would like the webservices to be invoked in parallel. > > Why? If it's so slow, try to optimize them. > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
