Hi! In Brief: Wrappers for individual contexts rather than hosts MixedDirContext JNDI wrapper providing access to slide and file system at same time.
Longer answers inserted between your text... On Fri, 2003-11-14 at 15:07, Stefano Mazzocchi wrote: > On 14 Nov 2003, at 11:32, Richard Unger wrote: > > > Hi! > > > > I was a little unhappy with the Tomcat integration, and I have written > > such a > > wrapper, which I would like to contribute. > > what does the wrapper do? > I have several wrappers. The original slide wrappers set up an entire tomcat host with the slide domain, mapping each namespace to a context. There were 2 such wrappers: one that set up each context so it would load its resources from the slide namespace it was associated with, but otherwise act as a normal tomcat context, and another wrapper that set up each context as a WEBDAV enabled context mapping to the namespace (ie with the webdav servlet behind it). That was the way it worked. I found this too restrictive, and added wrappers for an individual tomcat context instead of the entire host, permitting one to configure tomcat flexibly with webdav and slide resource contexts, as well as traditional web application contexts, as one chooses. In addition I added/fixed the ability to map a slide resource or webdav context to a subdirectory of the specified namespace. In order to implement the access to slide resources from a 'normal' tomcat context, a jndi resource wrapper (SlideDirContext wrapper) was written. This provides resources for the context, loading them from slide. Originally tomcat would load things from the WEB-INF directory of the context on disk, allowing web applications to be installed there, and then use the slide resources once the context was started. This behaviour changed at some point, loading all resources (even the WEB-INF dir) from slide when the wrapper was installed. Since I found it convenient, especially during testing, to keep jars on the file system and not have to load them into slide before starting the resource context, I wrote a MixedDirContext JNDI wrapper, which loads resources first from slide, and if not found there, from the filesystem. Its very useful for development. Where am I going with all this? I wanted to use more of WEBDAVs features to implement a CMS: I install the same slide namespace 3 times into tomcat: Once for public viewing as a resource context. Once for editing via online forms/webapps, also as a resource context, but the editing webapps talking to slide. Once for editing via webdav, as a webdav context. By enabling version control, and using the WEBDAV workspace feature, I can have the public and edit views show different versions of the same namespace. The edit context always maps to the main namespace (HEAD revision), while the public context maps to a workspace within the namespace, which is filled with the released version of files using the WEBDAV versioncontrol command. > > I'm motivated to contribute to the wrappers part of Slide, as I use > > this > > extensively myself. > > This would be welcome anyway. > > > I like the Slide Tomcat integration, but am I to understand that > > Tomcat is > > considered a piece of junk by the slide people? What exactly did you > > mean > > by 'piece of junk'? > > Remy is referring to the fact that I notoriously dislike Tomcat and > that Remy, nowadays being tomcat's lead developer and main cheerleader, > feels personally offended by this. > > It is wrong to identify my personal opinion with a general one. > Ok, I am relieved... I really like the fact that slide, as a webdav implementation works with any servlet container. At the same time I like the convenience of integration with tomcat, for those of us who can't afford websphere... > > Quoting Remy Maucherat <[EMAIL PROTECTED]>: > > > >> Oliver Zeigermann wrote: > >>> any help is appreciated! Maybe we should wait what Stefano might > >>> propose > >>> to decouple Slide from Tomcat even more. > >> > >> I can help fix the Tomcat integration eventually if it's broken (I did > >> it in the first place). > >> > >> It should be very obvious that Slide isn't coupled to Tomcat in any > >> way. > >> There are a few extra features: additional wrappers to allow webapps > >> to > >> be run from the Slide repository, with integrated security and an > >> admin > >> webapp to manage the users. At the time, I thought this was valuable > >> functionality. > >> > >> Of course, I understand one of Stephano's urges is apparently to get > >> rid > >> of that Tomcat piece of junk as soon as possible (it must be an > >> Italian > >> thing). Since you two are now in charge, you decide :) > > "Stefano", please. > > I'm not in charge of anything, I don't even get to vote here. > > -- > Stefano.
signature.asc
Description: This is a digitally signed message part
