> Folks, > > Back in a thread that ended on the 16th October we talked of some fixes > to the code that makes the interface abstractions ( interfaces & classes > in org.apache.catalina package ) no longer dependant on implementation > of Catalina. > > The reason we needed this is that it will make Catalina more mountable > in other applications. Interface/Impl separation allows classloader > hiding of impl from potentially hostile code. > > I guess many issues that were identified were fixed immediately. Here > is my view of what is left: > > org.apache.catalina.Cluster -> dependant on classes from > org.apache.catalina.cluster package > org.apache.catalina.Connector -> dependant on > org.apache.catalina.net.ServerSocketFactory > org.apache.catalina.Context -> dependant on many classes from > org.apache.catalina.deploy > org.apache.catalina.DefaultContext -> ditto > org.apache.catalina.Server -> ditto > > The consensus of opinion was to do nothing at that stage that might > break the API.
We tried (for some of the items), but it created lots of problems. We chose not to break the API, so none of the above will be "fixed" (although I don't consider any as a problem). > What is the feeling nearly three months on? Are we still aiming at full > separation in terms both of dependancy and Jar? Are these five fixable? No. Just package your JARs differently. cluster, deploy and net are self-contained packages, so just integrate them in the base package. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
