Pier Fumagalli wrote:
Yes, thanks.On 10/12/02 8:40 am, in article [EMAIL PROTECTED], "Remy Maucherat" <[EMAIL PROTECTED]> wrote:There is one big huge difference... Modules are DSOs, if you don't enable them in your httpd.conf, they don't get loaded, they don't get used.... Disabling all of them can be done by "sed 's/^LoadModule/#LoadModule/g'". If you get a binary distribution... (which, btw, doesn't enable most of them, it just _ships_ them in the same bundle...) If you don't get a binary distribution, when I build, I have a lot of tiny --enable and --disable flags... I can _choose_ what to build, what to install, what goes on my machine... This doesn't happen with Tomcat and it SUCKS ASS. :-) Don't compare yourself to HTTPD, learn from them, that's the only thing you can do... :-) (suggestion from someone who has been around long enough).
I don't see how the mechanism is very different from the Java CL and the Tomcat config files.
If you don't enable features in conf/server.xml and conf/web.xml, then the classes (which comprises the modules) don't get loaded, and the code is never run.
Not all classes get loaded by default, but all binaries are present. This also looks similar.
However, there's no convinient way to script enabling/disabling features, but I think that's more because we use XML, and its free form syntax.
Otherwise, for example: disable the Jasper module = remove stuff in conf/web.xml.
New signature! :-)
Great.
Lol. Yes, we all know webapp works for you (and hopefully other Solaris users). The problem is others.[...] mod_webapp, which was *the* main reason for many people not to adopt Tomcat 4.x - Remy Maucherat Works for me - Pier Fumagalli
Couldn't you have tried to work with others anyway ? (I did try, and it didn't hurt that much; I don't think Tomcat got worse because of Bill's and Costin's contributions, quite the contrary actually)
Remy
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
