Everything you describe is very common and has been solved a million times over, and are not particular to xml-rpc. Google for articles & tutorials on multi-tier web development with Java. What you probably want is an "application server", e.g. Apache Tomcat, that will provide things like database connection pooling for you. If you don't want something so heavy-weight, there are stand-alone libraries to do the same (look through Apache website). Maybe look at Hibernate, which I mention because you had the keywords "persistent object" in your post.
--Ryan Iain Bullard wrote: > Hello everyone, > > I need to access a (thread safe) persistent object from my xmlrpc > servlet. I > am currently using the > ServletWebServer with ws-xmlrpc 3.0, I have noticed that a class > specified > in the XmlRpcServlet.properties > will get initialised each time an xml-rpc request is made to it - is it > possible to initialise some before objects and > pass them to all my servlets init() method? > > In short: what is the easiest way to allow the servlet classes to access > persistent objects and are there any examples? > > I would ideally like to be able to reuse a pool of existing database > connections, which (in my mind anyway) > would appear to be a fairly common task for an xml-rpc based server. > As the > concept of spawning a new db > connection for each xml-rpc request is incredibly inefficient. > > Thanks, > > Iain. > -- Ryan Mitchell Engineering Development LogiTel Corp. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
