Philipp Meier wrote:
Both tomcat4 and jetty are servlet engines. It would IMHO make sense to make both provide sth. like "java-servlet-engine".
I don't think it makes sense. Sure, packages that contain webapps can depend on "java-servlet-engine" and put their webapp in /usr/share/java/webapps. But how do they tell any arbitrary servlet engine that provides the virtual package to activate this webapp?
So you gain nothing from this. It doesn't even make sense to package a webapp if it just contains a single .war file and depends on java-servlet-engine. You can as well copy the .war file to /usr/share/java/webapps (or the webapps directory of your favourite servlet engine).
If you really want to automatically setup your webapp from a Debian package, you need to depend on one or more specific servlet engines and tell them to active your webapp in your postinst.
> The debian java policy
doesn't mention anything in this way. If more than one servlet engine can be installed, how will /usr/share/java/webapps be handled?
tomcat4 just activates all webapps in this directory when it's started. Other servlet engines can do the same.
Stefan