Hi I've been following the discussions a bit lately. I used to also use the full-dist tomcat server distribution. There definitely needs to be done something about all this. See more comments inline.
Diego Bragato wrote: > > > Hi all, > > After a long discussion with Oliver (thanks Oliver ...) we managed to > arrive at the conclusion that the build.xml needs > refurbishment in the > release target. > > This is heavily significant to everybody: developers users > and community. > > As my understanding we all use slide in a large quantity of > flavors and > fashions. And as long as there are various needs around, it > needs a bit of > discussion to you all. > > What binary distributions you want to produce out of the > release target in > the build.xml ? > > The actual old way of producing jakarta-slide.2.0.0.tar.gz is > a tomcat > deployed in a non exactly standard way with a lot of old code. > Yep, I agree here. It's *very* obscure with all the different applications being deployed automagically over three different ports and there is NO documentation at all about how it all works. If I remember correctly this is how what happens: for each namespace 1. a vanilla webapp is deployed that is backed by SlideDirContext (all the resources are loaded from namespace/files) under a Host that is configured to run on port 8080. 2. a webdav webapp is deployed that has a servlet mapping of / to Slide WebDAV servlet. These are under a Host that is configured to run on port 8081. 3. an admin webapp is deployed under a Host that is configured to run under 8082. > There can be the need for a separate binary for the distribution of > 1 the slide client (this would be useful > to my personal project) > 2 out of the box build with tomcat 4.x (please propose me > a version) ideal > would be latest (this would be useful to my personal project) > 3 out of the box build with jboss (project www.jbpm.org > has one and it's > really nice) (this would be useful to my > personal project) > 4 a binary build with the needed wars and stuff for being > deployed in a > generic app server (see for example jetspeed project) maybe a > build.xml > can be needed for doing the deployment Sorry, but I don't think all this should be Slide's concern at all. What does Slide do ATM? 1. It's got a core repository and a WevDAV adapter in the form of a servlet. The way this is distributed in the servlet world is through a web archive. 2. Client app. Make an executable jar or a launch script. 3. WebDAV test suite Regards, Unico --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
