> -----Original Message----- > From: Steve Loughran [mailto:steve_l@;iseran.com] > Sent: Friday, November 01, 2002 10:40 AM > > ----- Original Message ----- > From: "KUMAR,PANKAJ (HP-Cupertino,ex1)" <[EMAIL PROTECTED]> > > > > > > My ISP allows me to have my own perl scripts. I would want > it to have my > own > > servlets but today it doesn't allow me that. Don't know if > there are ISPs > > that allow. But the deamnd is certainly there. The same > would hold for web > > services. Whether Axis can do this or not, with reasonable > overhead, would > > largely determine its acceptance within such environments. > > > if your ISP doesnt handle servlets/jsp, it wont take axis.
Thanks. I am enlightened !! > > > I realize that the current architecture of Axis, where Axis > runs as a > > servlet supporting all deployed web services, will be a > problem. This is > one > > area where I like the JAX-RPC RI architecture where each > web service is a > > separate servlet. With this comes isolation as one could > define the access > > rights of the code for each servlet separately. > > The trouble with isolation is that you have to be thorough. you need > isolated > -classloaders > -jndi > -jmx > -rpc > -anything else provided by the container > > servlet engines provide exactly this isolation between > webapps. There is no > point redoing this in axis, as all we'd end up doing is > reinventing stuff > and chasing security issues wherever we missed a bit. And > then we still > wouldnt integrate properly with the isolation provided by the > hosting app > server. That was exactly my point. The servlets provide the isolation. Axis, by deploying multiple web services within one servlet, breaks this isolation. One could, as suggested earlier in this thread, deploy one web service per axis servlet. But this is wasteful of memory and other resources as same libraries need to be duplicated in the memory at runtime ( maintainance of different versions of library is a "development time" issue and has no bearing on runtime efficiency -- reference to an earlier post within this thread ). My point was that the Axis architects should look at the option of improving the architecture so that a web service is deployed as a servlet. > > Its easy to add axis.jar to an existing webapp. lets stick > with what is > known, working and documented. For now, this is the "only" strategy possible. /Pankaj. > >
