As far as I know Spring is not 'single-threaded', its just how you design your beans. Most beans are meant to be used as stateless services, so the same service bean can be used by multiple threads because they are not changing state.
Spring doesn't handle stateful services because it is not an application server. If you want application state store it in the database or the webapp. Or get an application server and place it into a SFSB. And what is an 'infrastructure' person anyway? A systems admin? An architect? regards, Scott On Thursday 30 March 2006 07:49, Andrew Pym wrote: > I was speaking to an infrastructure person the other day about a badly > written EJB based application. > > For banter, I made some comments about tapestry/hivemind and spring. > > The main app server used at the company we are working at is WebLogic. > > The infrastructure guy complained about spring being single threaded and > had issues scaling horizonatally into clusters. > > Can someone enlighten me > > Is this a WebLogic issue with Spring? > A lack of knowledge about how to configure Spring? > Does the use of hivemind get around the single threaded spring issue, since > hivemind is a multi threaded registry/service model? > > What is the best setup to get horizontal scaling with Tapestry/hivemind? > What about if I have an app that includes Tapestry, hivemind and spring? > Can this be achieved with Jetty, Tomcat or Weblogic? > > > Regards > > Andrew > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
